From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Vimal <j.vimal@gmail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, Tom Tromey <tromey@redhat.com>,
gdb@sourceware.org
Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
Date: Sat, 05 Nov 2011 05:39:00 -0000 [thread overview]
Message-ID: <20111105053844.GA14861@host1.jankratochvil.net> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-11-05 5:39 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
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 [this message]
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=20111105053844.GA14861@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=j.vimal@gmail.com \
--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).