From: Stephen Smith <ischis2@home.com>
To: GDB <gdb@sourceware.cygnus.com>
Subject: Re: GDB and shared libraries
Date: Mon, 26 Feb 2001 20:51:00 -0000 [thread overview]
Message-ID: <3A9B3292.BFF1D69D@home.com> (raw)
In-Reply-To: <1010226233506.ZM13209@ocotillo.lan>
Let's pretend that my system is not SVR4 in nature and that I have source so a very minimal gdb server for an embedded
system that currently communicates with gdb for debugging of normal gcc applications.
Let's not assume that there are any special hooks in gdb for debugging shared libraries. What commands or data would
the gdb server have to send to gdb to enable the debugging of shared libraries.
Stephen
next prev parent reply other threads:[~2001-02-26 20:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A84136A.23BAF90F@home.com>
[not found] ` <1010209182220.ZM4621@localhost.localdomain>
[not found] ` <3A845A56.5EF8F61@home.com>
[not found] ` <3A9AB471.5F46554@home.com>
[not found] ` <1010226205415.ZM30678@localhost.localdomain>
2001-02-26 14:50 ` GDB and shared libraries (was Re: Are you still with Suse) Stephen Smith
2001-02-26 15:35 ` GDB and shared libraries Kevin Buettner
2001-02-26 16:07 ` Stephen Smith
2001-02-26 16:39 ` Stephen Smith
2001-02-26 18:05 ` Kevin Buettner
2001-02-26 20:51 ` Stephen Smith [this message]
[not found] ` <3A9B0022.16ABBBE0@home.com>
[not found] ` <1010227013252.ZM13444@ocotillo.lan>
2001-02-26 21:05 ` Stephen Smith
2001-02-26 23:10 ` Kevin Buettner
2001-02-27 7:37 ` Stephen Smith
2001-02-27 8:14 ` Andrew Cagney
2001-02-27 13:14 ` Stephen Smith
2001-02-27 13:44 ` Kevin Buettner
2001-02-27 14:04 ` Stephen Smith
2001-03-21 15:59 ` Stephen Smith
2003-07-24 21:51 gdb " wim delvaux
2004-01-06 22:07 GDB and Shared Libraries Drummonds, Scott B
2004-01-06 22:10 ` Daniel Jacobowitz
2006-02-08 21:13 gdb and shared libraries Patrick Alken
2006-02-09 5:54 ` Jim Blandy
2006-02-09 13:51 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A9B3292.BFF1D69D@home.com \
--to=ischis2@home.com \
--cc=gdb@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox