-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I got this error message if I try to debug a program in C: Warning: Cannot insert breakpoint -2. Error accessing memory address 0x4000bb50: Input/output error. The same program may be running in another process. Obiously there is no other process executing that program. Is my gdb screwed? How can I solve it? I am using Suse 8.2 with the same gcc and gdb that are on cds. Praise -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/N/US6v3ZTabyE8kRAnZSAJ429cIPD4lUQoLUOQ6YNpUtiYd9GACeL209 Z5kBEqRm7uJ4YwrNBIcq+LU= =UCwR -----END PGP SIGNATURE-----
Hi Praise, Try to searth for the bug on http://www.gnu.org/software/gdb/bugs/ . Hope it helps! Hälsningar/Regards - Tommy Rönnholm ======================================= Tel/phone: 070-6400232 Int: +46(70)6400232 Fax: 070-3889387 Int: +46(70)3889387 tommy.ronnholm@elcaro.se http://www.elcaro.se
-----Original Message----- From: Praise [mailto:praisetazio@tiscalinet.it] Sent: Monday, August 11, 2003 9:57 PM To: suse-programming-e@suse.com Subject: [suse-programming-e] gdb screwed?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I got this error message if I try to debug a program in C:
Warning: Cannot insert breakpoint -2. Error accessing memory address 0x4000bb50: Input/output error. The same program may be running in another process.
Obiously there is no other process executing that program. Is my gdb screwed? How can I solve it?
I am using Suse 8.2 with the same gcc and gdb that are on cds.
Praise -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQE/N/US6v3ZTabyE8kRAnZSAJ429cIPD4lUQoLUOQ6YNpUtiYd9GACeL209 Z5kBEqRm7uJ4YwrNBIcq+LU= =UCwR -----END PGP SIGNATURE-----
-- To unsubscribe, email: suse-programming-e-unsubscribe@suse.com For additional commands, email: suse-programming-e-help@suse.com Archives can be found at: http://lists.suse.com/archive/suse-programming-e
Alle 22:24, lunedì 11 agosto 2003, Tommy Rönnholm ha scritto:
Hi Praise,
Try to searth for the bug on http://www.gnu.org/software/gdb/bugs/ .
Hope it helps!
Hälsningar/Regards - Tommy Rönnholm
It helped. Unfortunately there is no fix to this problem. I found this (horrible) URL: http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1219&return_url=http%3A%2F%2Fsources.redhat.com%2Fcgi-bin%2Fgnatsweb.pl%3Fdatabase%3Dgdb%26category%3Dbreakpoints%26severity%3Dcritical%26priority%3Dall%26responsible%3Dall%26submitter_id%3Dall%26state%3Dall%26ignoreclosed%3DIgnore%2520Closed%26class%3Dall%26synopsis%3D%26multitext%3Dbreakpoint%26columns%3Dcategory%26columns%3Dstate%26columns%3Dclass%26columns%3Dresponsible%26columns%3Dsynopsis%26displaydate%3DDisplay%2520Current%2520Date%26cmd%3Dsubmit%2520query%26sortby%3DResponsible%26.cgifields%3Ddisplaydate%26.cgifields%3Dignoreclosed%26.cgifields%3Doriginatedbyme%26.cgifields%3Dcolumns Just wonder if there is an upgrate/downgrade to avoid this. Praise
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alle 22:24, lunedì 11 agosto 2003, Tommy Rönnholm ha scritto:
Hi Praise,
Try to searth for the bug on http://www.gnu.org/software/gdb/bugs/ .
Hope it helps!
Hälsningar/Regards - Tommy Rönnholm
For those who did not remember, my gdb could not access the debugged program own memory. After having tried a lot of stuff (reinstalling, recompiling gdb, and so on...) I have found what the problem is. If the executable file is on an XFS filesystem, gdb cannot access its own memory. If it is on ReiserFS, it can. So the turn around is: do not use XFS for programming! I am going to try out wether it works if I use a loopback filesystem, and I am going to send a feedback to suse too. Praise -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/PgIQ6v3ZTabyE8kRAiUcAKDAq8oSBXx3jYUuxqJ5ZHtNAXDTAwCgnLzy m0O5132AxW79zoUdsisDX0c= =bCQ7 -----END PGP SIGNATURE-----
participants (3)
-
Alice -
Praise
-
Tommy Rönnholm