From: Jan Kiszka <jan.kiszka@web.de>
To: tromey <tromey@redhat.com>
Cc: Vimal <j.vimal@gmail.com>, gdb@sourceware.org
Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
Date: Thu, 27 Oct 2011 00:22:00 -0000 [thread overview]
Message-ID: <4EA89365.2010807@web.de> (raw)
In-Reply-To: <CAK3Ji13Vwh9ZBENNtBkuHfqww1=OhcUGKeCWwgYVmT++a5c4UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-10-26 23:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 2:20 Vimal
2011-10-24 14:11 ` Vimal
2011-10-26 12:25 ` Vimal
2011-10-27 0:22 ` Jan Kiszka [this message]
2011-10-27 0:43 ` Vimal
2011-10-27 7:21 ` Jan Kiszka
2011-10-27 14:59 ` Vimal
2011-10-27 16:12 ` Jan Kiszka
2011-10-28 0:16 ` Tom Tromey
2011-10-31 17:20 ` Jan Kiszka
2011-10-27 19:38 ` Tom Tromey
2011-10-28 3:40 ` Vimal
2011-10-28 21:07 ` Vimal
2011-10-31 17:18 ` Jan Kiszka
2011-10-31 21:33 ` Tom Tromey
2011-11-01 15:32 ` Jan Kiszka
2011-11-01 20:13 ` Jan Kratochvil
2011-11-05 2:07 ` Vimal
2011-11-05 5:39 ` Jan Kratochvil
2011-11-08 0:33 ` Jan Kratochvil
2011-11-05 2:10 ` Vimal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA89365.2010807@web.de \
--to=jan.kiszka@web.de \
--cc=gdb@sourceware.org \
--cc=j.vimal@gmail.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox