[SLE] gdb problems slowing developement - possible problem with glibc ?

Hi, I am having some painful problems with gdb, and any help would be really appreciated. 1) breakpoints in shared libraries: If I set breakpoints in functions which are in shared libraries, when I restart the program gdb complains with the following message: /path/to/program/to/debug: error in loading shared libraries: libXX.so.1: failed to map segment from shared object: Cannot allocate memory The only option I have is to disable the breakpoints, set a breakpoint at "main" and then enable the breakpoints again :-( 2) The line numbers which are being reported by gdb do not correspond with the line numbers in the source file - even though the up-to-date file is actually loaded into the debugger, the library has been compiled with the loaded file, and the compiled library has been loaded! Possibly 1) above affected this ? And some other data: system is SuSE 6.4 which means that gdb rpm gdb-4.18-81 Problem 1) occurred many months ago and I am almost sure that it was after migrating from an older version of SuSE ( 5.3 to 6.1 ), so maybe it is because of the glibc migration ?? Problem 2) only seems to have occurred since I migrated from SuSE 6.3 to 6.4. However I did have some migration problems ( e.g. the gdb version was not updated correctly ), so could anyone suggest a possible cause of the above ? Thanks for all your help, CP -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

For those interested, it seems that this is really a problem of interaction between gdb and glibc. It looks like the next release of gdb will solve the problem. CP -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (1)
-
CP.Hennessy@iname.com