Re: How does the dynamic loader (libdl) hook in to gdb?

2020-01-22 Thread dufault
> On Jan 21, 2020, at 15:59 , dufa...@hda.com wrote: > > - I've modified "libdl" to generate a report of the sections that GDB expects > to receive in response the that query. It's almost what is present to > support the special RTEMS target stub, but you've collapsed the number of >

Re: How does the dynamic loader (libdl) hook in to gdb?

2020-01-21 Thread dufault
> On Jan 20, 2020, at 17:37 , Chris Johns wrote: > > Hi Peter, > > Happy new year. > > On 17/1/20 9:01 am, Peter Dufault wrote: >> I'm trying to hook the SLAC / Til Straumann PowerPC remote debugger stub in >> to what's loaded by "libdl" via "dlopen()". *I know* this should be >>

Re: How does the dynamic loader (libdl) hook in to gdb?

2020-01-20 Thread Chris Johns
Hi Peter, Happy new year. On 17/1/20 9:01 am, Peter Dufault wrote: > I'm trying to hook the SLAC / Til Straumann PowerPC remote debugger stub in > to what's loaded by "libdl" via "dlopen()". *I know* this should be > integrated into "libdebugger", and I do keep my eye on that, but I need to

How does the dynamic loader (libdl) hook in to gdb?

2020-01-16 Thread Peter Dufault
I'm trying to hook the SLAC / Til Straumann PowerPC remote debugger stub in to what's loaded by "libdl" via "dlopen()". *I know* this should be integrated into "libdebugger", and I do keep my eye on that, but I need to keep what is working working and working well. The "libdl" code has