From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Michael Snyder <msnyder@vmware.com>,
"?$BPd?pzx" <niruiyu@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Can GDB stub report every module loading event so that the host can load every module symbol automatically?
Date: Tue, 27 Apr 2010 02:57:00 -0000 [thread overview]
Message-ID: <w2ldaef60381004261957j9cfdda4fha6036d27e6975ada@mail.gmail.com> (raw)
In-Reply-To: <g2ydaef60381004261947gdfb21aach5f2ace9a88ec24c8@mail.gmail.com>
On Tue, Apr 27, 2010 at 10:47, Hui Zhu <teawater@gmail.com> wrote:
> On Tue, Apr 27, 2010 at 01:36, Joel Brobecker <brobecker@adacore.com> wrote:
>>> There is no such message because the stub doesn't know
>>> anything about modules. There is no particular "event"
>>> when execution first enters a module.
>>
>> Could these modules be seen as "shared libraries"? The remote protocol
>> supports that...
>>
>
> I think we have 2 trouble about it:
> 1. Some stub for example a qemu, let itself set the breakpoint to
> stop the event and get the lib name and address is not easy.
> 2. For GDB part, let it know where is the solib in sometime is not
> easy. For example, cross compile kernel will be put to anywhere and
> each module will be put a different dir.
>
http://sourceware.org/ml/gdb/2010-02/msg00022.html
This thread is talk about LKM in before.
Regards,
Hui
prev parent reply other threads:[~2010-04-27 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 7:36 倪瑞煜
2010-04-26 17:21 ` Michael Snyder
2010-04-26 17:36 ` Joel Brobecker
2010-04-27 2:47 ` Hui Zhu
2010-04-27 2:57 ` Hui Zhu [this message]
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=w2ldaef60381004261957j9cfdda4fha6036d27e6975ada@mail.gmail.com \
--to=teawater@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=niruiyu@gmail.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