public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Vimal <j.vimal@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
Date: Thu, 27 Oct 2011 00:43:00 -0000	[thread overview]
Message-ID: <CAK3Ji10OMuDo09U--JYxtFbLOUP1+AbGxD01O5xWi1BgR19Zxw@mail.gmail.com> (raw)
In-Reply-To: <4EA89365.2010807@web.de>

Hi Jan,

Well, I am glad that the bug is reproduced by someone else. :)

On 26 October 2011 17:10, Jan Kiszka <jan.kiszka@web.de> wrote:
>
> 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.
>

Could be, but it points to a bunch of commits that could be a potential problem.

>
> 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... ;)

Maybe you can use gdb version before that particular commit?

I've filed a bug report, which lists some variants of the bug:
http://sourceware.org/bugzilla/show_bug.cgi?id=13346

Thanks,
-- 
Vimal

  reply	other threads:[~2011-10-27  0:22 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 [this message]
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=CAK3Ji10OMuDo09U--JYxtFbLOUP1+AbGxD01O5xWi1BgR19Zxw@mail.gmail.com \
    --to=j.vimal@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kiszka@web.de \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).