Multiple breakpoint issue when debugging loadable kernel module
Jan Kiszka
jan.kiszka@web.de
Thu Oct 27 00:22:00 GMT 2011
On 2011-10-25 04:57, Vimal wrote:
> Hi,
>
> With some suggestions from IRC folks sergiodj and SamB, I ran a git
> bisect on the HEAD of git://sourceware.org/git/gdb.git.
>
> It seems like the first bad commit is:
> 2cdbbe44126601596aad7891de05cb7fc6bb21c8, which seems pretty big
> ~6000lines.
Wow, that saved me a lot of time. I just ran into the same issue and was
close to getting mad over the effect.
Maybe the commit is only that big because cvs-to-git conversion merged
too much into a single commit. I can't imagine that such a huge change
is done in one step.
>
> Quoted below is my first mail to the list, with few details about the
> problem. Also, here's an output from an actual run:
> http://pastebin.com/4PhDAHwW...
>
> Tom Tromey: is this a known issue?
At least it is a critical one as it makes kernel module debugging nearly
impossible. I'm preparing a LinuxCon talk about how cool kernel
debugging with gdb and qemu can be - looks like I have to skip this
part... ;)
If there is anything to be done that could help analyzing the issue,
please let us know.
Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://sourceware.org/pipermail/gdb/attachments/20111027/d338db99/attachment.sig>
More information about the Gdb
mailing list