Re: tlug: debugging shared objects

[Scott Stone <sstone@example.com>]

On Mon, 7 Dec 1998, Marcus Metzler wrote:

> Scott Stone writes:
>  > 
>  > OK, if I have a known-stable program A and an in-development shared object
>  > B, which is designed to be dlopen()'ed by A, how do I set breakpoints
>  > inside object B's code with GDB?  ie, everything is built with -g and is
>  > not stripped.. so I run 'gdb A' and then...?  What's the command to set
>  > the breakpoint inside the code for shared object module B?
>  > 
> You should be able to set a breakpoint via the name of one of the
> subroutines in module B, i.e. b subroutine. Then you can run the
> program until it gets to that subroutine and it should show you the
> line numbers of module B when you use list. Then you can set the
> breakpoint by using line numbers. I think it is also possible to tell
> gdb to "load" the source code of module B and than use "b linenumber"
> to set the breakpoint, but I haven`t tried that.

apparently not.  I can't 'b subroutine', though, until the symbols from
the shared object are loaded - this is what I'm unable to do.  I can work
around it by setting a breakpoint where the dlopen() happens.  After that
line, I can set breakpoints wherever I want to... 

--------------------------------------------------
Scott M. Stone <sstone@example.com, sstone@example.com>
Head of TurboLinux Development/Systems Administrator
Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)


------------------------------------------------------------------
Next Technical Meeting: 12 December, 12:30 at Temple Univ. Japan
*NEW LOCATION* a map is available at http://www.tuj.ac.jp/maps.html
Next Nomikai: 15 January 1999, 19:30 Tengu TokyoEkiMae 03-3275-3691
------------------------------------------------------------------
more info: http://tlug.linux.or.jp                     Sponsor: PHT