From: Jim Blandy <jimb@cygnus.com>
To: gdb-patches@cygnus.com
Subject: Re: none
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <nppv6jvllo.fsf@zwingli.cygnus.com> (raw)
Message-ID: <19990401000000.jY_VXLmfar_tYfvHBdjQbNEy2KBa8aFssEPEitidqAY@z> (raw)
In-Reply-To: <99030817102600.14026@hal>
> Some global symbols are defined in gdb/main.c (eg. gdb_stdout,
> gdb-stderr, etc). As the result if I'm building all except main.c in
> object library to use with some IDE that uses gdb for debugging
> (rhide-1.4.7), I'm getting unresolved references.
Um, wow. It never occurred to me that anyone would try that.
Specifically, we can't include GCC-specific things like the
constructor attribute in GDB's source code. Lots of people build GDB
with compilers other than GCC.
I'm not the GDB Maintainer --- that'd be Dr. Shebs --- but my feeling
is that we don't want to get into maintaining GDB with this kind of
application in mind. If we turn GDB into a library, we should do it
right --- design an interface that makes sense, document the
interface, make sure that future changes preserve the boundaries, etc.
My guess is that that would be more work than we really want to take
on.
> An alternative idea could be duplicating init code and global
> vrariables in rhide.
I think this is your best bet.
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-08 7:10 No Subject Andris Pavenis
1999-03-08 11:15 ` Jim Blandy [this message]
1999-04-01 0:00 ` libgdb (was none) Robert Hoehne
1999-03-08 14:31 ` Robert Hoehne
1999-04-01 0:00 ` Stan Shebs
1999-03-10 15:39 ` Stan Shebs
1999-03-10 16:29 ` Todd Whitesel
1999-04-01 0:00 ` Todd Whitesel
1999-03-14 4:18 ` Robert Hoehne
1999-04-01 0:00 ` Robert Hoehne
1999-04-01 0:00 ` DJGPP support (was libgdb) Stan Shebs
1999-03-14 14:41 ` Stan Shebs
1999-04-01 0:00 ` none Stan Shebs
1999-03-08 13:09 ` none Stan Shebs
1999-03-09 12:54 ` none Robert Hoehne
1999-04-01 0:00 ` none Robert Hoehne
1999-04-01 0:00 ` none Jim Blandy
[not found] ` <99031011141900.03735.cygnus.patches.gdb@hal>
1999-03-10 16:31 ` libgdb.a Andrew Cagney
1999-04-01 0:00 ` libgdb.a Andrew Cagney
1999-04-01 0:00 ` libgdb.a Andris Pavenis
1999-03-11 0:27 ` libgdb.a Andris Pavenis
1999-04-01 0:00 ` libgdb.a Todd Whitesel
1999-03-10 16:56 ` libgdb.a Todd Whitesel
1999-03-11 12:40 ` libgdb.a Stan Shebs
1999-04-01 0:00 ` libgdb.a Stan Shebs
1999-04-01 0:00 ` libgdb.a J.T. Conklin
1999-03-11 14:29 ` libgdb.a J.T. Conklin
1999-04-01 0:00 ` No Subject Andris Pavenis
1999-04-01 0:00 ` libgdb.a Andris Pavenis
1999-03-10 1:14 ` libgdb.a Andris Pavenis
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=nppv6jvllo.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=gdb-patches@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