From: Stan Shebs <shebs@cygnus.com>
To: toddpw@wrs.com
Cc: gdb-patches@cygnus.com
Subject: Re: libgdb.a
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199903112040.MAA03640@andros.cygnus.com> (raw)
Message-ID: <19990401000000.jq984exkNCD6T_YZnWl94YtOX6Z0HyQ-8wK4q2RdUck@z> (raw)
In-Reply-To: <199903110056.QAA00306@alabama.wrs.com>
From: toddpw@wrs.com (Todd Whitesel)
Date: Wed, 10 Mar 1999 16:56:04 -0800 (PST)
I would love it if more things in GDB were "constructored" and not #define'd
or hardcoded. Right now (read 4.17) with many remote targets you can't know
the exact register list until you probe the target to find out what it is,
yet the reg_names[] array is statically initialized (because on ptrace unix
platforms that Just Worked), and we're just lucky that the rest of GDB adapts
well to having reg_names[] edited after initialization.
As I mentioned a couple weeks ago to one of the lists, more dynamic
construction is the way to go in the future. One thing that individuals
can do now to ease the transition is to avoid ifdefs in their patches.
It should be clear to everyone that a GDB littered with target ifdefs
is not going to be able to make runtime choices about anything. So,
avoid the ifdef!
Stan
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 ` 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 J.T. Conklin
1999-03-11 14:29 ` libgdb.a J.T. Conklin
1999-04-01 0:00 ` libgdb.a Andrew Cagney
1999-04-01 0:00 ` libgdb.a Todd Whitesel
1999-03-10 16:56 ` libgdb.a Todd Whitesel
1999-03-11 12:40 ` Stan Shebs [this message]
1999-04-01 0:00 ` libgdb.a Stan Shebs
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 Andris Pavenis
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=199903112040.MAA03640@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb-patches@cygnus.com \
--cc=toddpw@wrs.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