CyberPsychotic wrote: > > > questions: > > > Core was generated by 'AAAAA...' > > > what does it mean? core generated when gdb tried to execute this piece > > > of code? or, just this piece of string went out the segment? > > > > It probably means that the core dump is bogues, e.g. because the > > relevant part of memory has been corrupted. The string following the > > `Core was generated by' message should be the name of the program. > > so that code (actually the long line of 'AAA..' was passed as one of env. > variable) overwritten the part of memory, where kernel saves the name of > loaded code, right? That would be my guess. > > However, you can't get much useful information out of a core file > > unless the program was built with debugging info. And if you want to > > get details of the execution context for code > > hmm.. like data passed to library routine, etc, right? Like parameters or local variables of a library function. > > that is part of a > > library, then the library needs to be built with debug info also. > > is there a way to specify what library to use while running > codes compiled in debug mode *(say if i want only single code to work > with debugging-mode library) or i would have to replace link in > /usr/lib|lib and thus make it for all system processes..(sorry if sounds > abit confusing) Debug libraries are usually static; you would normally give the full pathname to the library (e.g. /usr/lib/libfoo.a) to the gcc command, rather than using -lfoo. -- Glynn Clements <[EMAIL PROTECTED]>
