From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Smith To: GDB Subject: Re: GDB and shared libraries Date: Mon, 26 Feb 2001 21:05:00 -0000 Message-id: <3A9B35E4.33B1868B@home.com> References: <3A84136A.23BAF90F@home.com> <1010209182220.ZM4621@localhost.localdomain> <3A845A56.5EF8F61@home.com> <3A9AB471.5F46554@home.com> <1010226205415.ZM30678@localhost.localdomain> <3A9ADDF4.FD998D6E@home.com> <1010226233506.ZM13209@ocotillo.lan> <3A9B0022.16ABBBE0@home.com> <1010227013252.ZM13444@ocotillo.lan> X-SW-Source: 2001-02/msg00405.html Ah, now I know why we are not communicating. I have an embedded system with a proprietary OS. This system has a minimal gdb server running on it. Let's call this the target system. My host is a Windows NT/Cygwin or Linux Box running gdb which is talking to the gdb server on the target machine. The problem is that I have a process running on the target (no video, X, etc.) and am debugging on the host. My process uses a shared library and I need to add the capability of tracing into it. Ok, what do I need to add (commands, data, etc.) to my gdb server to trace into these libraries? Is the spec written down? Kevin Buettner wrote: > On Feb 26, 6:17pm, Stephen Smith wrote: > > > I am told that the "minimal" (and I don't know how minimal) > > gdbserver doesn't follow the SVR4 spec. Well, I could have fun. > > Okay, you've lost me. Where does gdbserver enter into the picture? > > Kevin