This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Multiple breakpoint issue when debugging loadable kernel module
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Vimal <j dot vimal at gmail dot com>
- Cc: Jan Kiszka <jan dot kiszka at web dot de>, Tom Tromey <tromey at redhat dot com>, gdb at sourceware dot org
- Date: Sat, 5 Nov 2011 06:38:44 +0100
- Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
- References: <CAK3Ji13Vwh9ZBENNtBkuHfqww1=OhcUGKeCWwgYVmT++a5c4UQ@mail.gmail.com> <4EA89365.2010807@web.de> <m3aa8mb58w.fsf@fleche.redhat.com> <CAK3Ji109-gd-zHfYSW70XEubPuugW8KRD5o08z5Qfug+f0LSNQ@mail.gmail.com> <CAK3Ji13FeEtpsq80eAwsyQo+xxSyiyjhDQ=MKXniXJr-d1p2Fg@mail.gmail.com> <4EAED7DC.5030805@siemens.com> <m3y5w051d6.fsf@fleche.redhat.com> <4EB010D1.9050209@web.de> <20111101201247.GA19887@host1.jankratochvil.net> <CAK3Ji11N2cTi=okhp7PfTdpy37xM7u-6ijAu3whC2E8xgftRJw@mail.gmail.com>
On Sat, 05 Nov 2011 03:06:50 +0100, Vimal wrote:
> As I am not experienced enough with this, would love some more
> pointers.
You can also send me offlist the .ko file.
> Are you suggesting gcc does not insert debug information correctly?
Yes.
> Though this is possible, does it explain the fact that
> the same .ko file without recompilation, works with gdb-7.1?
Yes, as this buggy information is there only to direct GDB which CUs
(Compilation Units) need to be expanded, if GDB expands them excessively it
does not need this information, if GDB expands them optimally then the debug
info bug starts to expose.
I do not say this is the bug but I find it probable and checking the debug
info is the most easy first step while troubleshooting it.
Thanks,
Jan