From: Andris Pavenis <andris@stargate.astr.lu.lv>
To: gdb-patches@cygnus.com
Subject: Re: libgdb.a
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <99031011141900.03735@hal> (raw)
In-Reply-To: <99030817102600.14026@hal>
On Mon, 08 Mar 1999, Andris Pavenis wrote:
>Hi!
>
>Tried gdb-4.17.85 on i586-pc-linux-gnu (with glibc-2.1) and met following
>problem that was no with gdb-4.17:
>
>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.
>
>So I'm suggesting rather ugly hack (moving these definitions to top.c
>and puting there static constructor that initializes gdb_std*). I agree does
>not look nice, but I'm sending it only to point to possible problem.
>I cannot use _initialize_* here as files must be defined before running
>all _initialize_* procedures.
>
Maybe it would be usefull to implement init functions of higher priority that
are executed before ones which names begins with _initialize_.
So we would be able to avoid gcc related extensions such as
__attribute__((constructor)).
For that we should use a different name prefix (eg. _preinit_ or something like)
and require that these functions are independent one from another one (should
not use results of other similar init functions).
Andris
Please send answers also to me as I'm not subscribed to gdb-patches
WARNING: multiple messages have this Message-ID
From: Andris Pavenis <andris@stargate.astr.lu.lv>
To: gdb-patches@cygnus.com
Subject: Re: libgdb.a
Date: Wed, 10 Mar 1999 01:14:00 -0000 [thread overview]
Message-ID: <99031011141900.03735@hal> (raw)
Message-ID: <19990310011400.OvK2ypwzfyjPifr4EgZnMabmtEuE-VghLUefI9-UAQw@z> (raw)
In-Reply-To: <99030817102600.14026@hal>
On Mon, 08 Mar 1999, Andris Pavenis wrote:
>Hi!
>
>Tried gdb-4.17.85 on i586-pc-linux-gnu (with glibc-2.1) and met following
>problem that was no with gdb-4.17:
>
>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.
>
>So I'm suggesting rather ugly hack (moving these definitions to top.c
>and puting there static constructor that initializes gdb_std*). I agree does
>not look nice, but I'm sending it only to point to possible problem.
>I cannot use _initialize_* here as files must be defined before running
>all _initialize_* procedures.
>
Maybe it would be usefull to implement init functions of higher priority that
are executed before ones which names begins with _initialize_.
So we would be able to avoid gcc related extensions such as
__attribute__((constructor)).
For that we should use a different name prefix (eg. _preinit_ or something like)
and require that these functions are independent one from another one (should
not use results of other similar init functions).
Andris
Please send answers also to me as I'm not subscribed to gdb-patches
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 ` none Jim Blandy
1999-04-01 0:00 ` none Jim Blandy
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 ` 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 ` DJGPP support (was libgdb) Stan Shebs
1999-03-14 14:41 ` Stan Shebs
1999-04-01 0:00 ` libgdb (was none) Robert Hoehne
[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 ` Andris Pavenis [this message]
1999-03-10 1:14 ` libgdb.a Andris Pavenis
1999-04-01 0:00 ` No Subject 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=99031011141900.03735@hal \
--to=andris@stargate.astr.lu.lv \
--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