From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vimal <j.vimal@gmail.com>
Cc: tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: Multiple breakpoint issue when debugging loadable kernel module
Date: Thu, 27 Oct 2011 16:12:00 -0000 [thread overview]
Message-ID: <4EA97C82.1070201@siemens.com> (raw)
In-Reply-To: <CAK3Ji11vqHB+FFx8rCAMHAvZ+VGD276jPO1tLjp-QaUCCvCm3w@mail.gmail.com>
On 2011-10-27 16:47, Vimal wrote:
> On 27 October 2011 01:10, Jan Kiszka <jan.kiszka@web.de> wrote:
>>
>> That's what I'm doing right now, but I'd like to use [1] and maybe write
>> some more helpers. :)
>
> Jan,
>
> I have written a script for listing loaded modules as well and it is
> possible with the gdb version 7.1, just before the faulty commit.
>
> I am not sure if gdb.selected_frame() is available, but, since
> "modules" is a global variable, you could just use parse_and_eval.
> That should work. :)
Yeah, I just had to hack that version to accept python 2.7 - all
features there, and my script works as-is.
>
> Good luck on your presentation!
>
Thanks!
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-10-27 15:45 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 [this message]
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=4EA97C82.1070201@siemens.com \
--to=jan.kiszka@siemens.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).