Can GDB stub report every module loading event so that the host can load every module symbol automatically?

Can GDB stub report every module loading event so that the host can load every module symbol automatically?

[倪瑞煜]

Hi,

I want my GDB stub to report every module loading event so that the
GDB in the host can receive the message and load every module symbol
automatically during my OS booting.
I searched the GDB serial protocol but didn't find any message can
meet my requirement.
Can anyone kindly help me on this?

Thanks,
Ruiyu

Re: Can GDB stub report every module loading event so that the host can load every module symbol automatically?

[Michael Snyder]

倪瑞莘 wrote:
> Hi,
> 
> I want my GDB stub to report every module loading event so that the
> GDB in the host can receive the message and load every module symbol
> automatically during my OS booting.
> I searched the GDB serial protocol but didn't find any message can
> meet my requirement.
> Can anyone kindly help me on this?
> 
> Thanks,
> Ruiyu

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.

Re: Can GDB stub report every module loading event so that the host can load every module symbol automatically?

[Joel Brobecker]

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

-- 
Joel

Re: Can GDB stub report every module loading event so that the host can load every module symbol automatically?

[Hui Zhu]

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.

Regards,
Hui

Re: Can GDB stub report every module loading event so that the host can load every module symbol automatically?

[Hui Zhu]

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