From: Tom Tromey <tromey@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Vimal <j.vimal@gmail.com>, gdb@sourceware.org
Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
Date: Thu, 27 Oct 2011 19:38:00 -0000 [thread overview]
Message-ID: <m3aa8mb58w.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4EA89365.2010807@web.de> (Jan Kiszka's message of "Thu, 27 Oct 2011 01:10:29 +0200")
>>>>> "Jan" == Jan Kiszka <jan.kiszka@web.de> writes:
Jan> At least it is a critical one as it makes kernel module debugging nearly
Jan> impossible. I'm preparing a LinuxCon talk about how cool kernel
Jan> debugging with gdb and qemu can be - looks like I have to skip this
Jan> part... ;)
Well, we can't let that happen.
Jan> If there is anything to be done that could help analyzing the issue,
Jan> please let us know.
A recipe to reproduce the bug. I know nothing about the kernel, so if
it requires extensive setup, precise instructions would be best.
We've been poking at it a bit on irc but, aside from a lot of weird and
inexplicable gdb behavior, we haven't seen anything too useful.
Tom
next prev parent reply other threads:[~2011-10-27 19:32 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
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 [this message]
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=m3aa8mb58w.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=j.vimal@gmail.com \
--cc=jan.kiszka@web.de \
/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