[Lazarus] Debugging shared libraries

[Mark Morgan Lloyd]

Henry Vermaak wrote:
> On 16/09/12 14:26, Mark Morgan Lloyd wrote:
>> I've developed a useful convention which allows me to either load a
>> library on demand (via Dynlibs) or to link it statically. This
>> combination allows me to use standard Lazarus debugging techniques to
>> sort out most problems.
>>
>> However, yesterday's discussion about calling /from/ a
>> dynamically-loaded library /into/ a program binary (other than the main
>> program) raises an interesting question: can Lazarus+gdb be persuaded to
>> trace into a shared library?
> 
> Whenever I've tried, Lazarus hasn't had any problems stepping into my
> libraries (written in C).  I usually don't use a debugger, though, so my
> experience is limited.

On Linux, if loading a library (written using Lazarus) using DynLibs, 
I've not managed to get further in than the variable containing a 
pointer to the entry point. I could be missing something, but I don't 
think that Lazarus+gdb has a way of pulling in the symbolic info from 
the .so binary.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]