https://community.hpe.com/t5/operating-system-hp-ux/core-dump-on-getenv/m-p/3332756#M712352 We are getting a core dump on the getenv call of an older application we are porting to 11.0 64 bit. THis was a c application. We are compiling with -Ae and -DA2.0W. Can't find any patches for libc that mention this behavior - any clues? Thu, 15 Jul 2004 12:56:19 GMT Michael Murphy_2 2004-07-15T12:56:19Z https://community.hpe.com/t5/operating-system-hp-ux/core-dump-on-getenv/m-p/3332756#M712352 We are getting a core dump on the getenv call of an older application we are porting to 11.0 64 bit. THis was a c application. We are compiling with -Ae and -DA2.0W. Can't find any patches for libc that mention this behavior - any clues? Thu, 15 Jul 2004 12:56:19 GMT https://community.hpe.com/t5/operating-system-hp-ux/core-dump-on-getenv/m-p/3332756#M712352 Michael Murphy_2 2004-07-15T12:56:19Z https://community.hpe.com/t5/operating-system-hp-ux/core-dump-on-getenv/m-p/3332757#M712353 Your code might have a 64-bit porting issue. Perhaps you passed in a bad pointer or assigned the result of getenv to a bad address for a pointer. You could see that by running the gdb debugger on the program and core file and using the 'disas' and 'info reg' commands to see where the crash happened and what data it was working on.<BR />Another surprisingly common way to crash in getenv is to use putenv with a string constant that is defined in a shared library, then unload that shared library. The string address is unmapped, so the next getenv call gets a segmentation fault. Thu, 15 Jul 2004 15:08:53 GMT https://community.hpe.com/t5/operating-system-hp-ux/core-dump-on-getenv/m-p/3332757#M712353 Mike Stroyan 2004-07-15T15:08:53Z