From: toddpw@wrs.com (Todd Whitesel)
To: gdb-patches@cygnus.com
Subject: Re: libgdb.a
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199903110056.QAA00306@alabama.wrs.com> (raw)
In-Reply-To: <36E70EE3.3D0937F1@cygnus.com>
>target-architectures during startup, it would probably be more prudent to leave
>most of that task until the point where GDB knew exactly which architecture was
>being debugged.
Yes, and this sounds like an example where multi-level initialization is a
Good Thing(TM).
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.
--
Todd Whitesel
toddpw @ wrs.com
WARNING: multiple messages have this Message-ID
From: toddpw@wrs.com (Todd Whitesel)
To: gdb-patches@cygnus.com
Subject: Re: libgdb.a
Date: Wed, 10 Mar 1999 16:56:00 -0000 [thread overview]
Message-ID: <199903110056.QAA00306@alabama.wrs.com> (raw)
Message-ID: <19990310165600.h7TwvdzQttutKwQ5JBMQGrHj2UXTgxJD5xzPP9kBQkA@z> (raw)
In-Reply-To: <36E70EE3.3D0937F1@cygnus.com>
>target-architectures during startup, it would probably be more prudent to leave
>most of that task until the point where GDB knew exactly which architecture was
>being debugged.
Yes, and this sounds like an example where multi-level initialization is a
Good Thing(TM).
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.
--
Todd Whitesel
toddpw @ wrs.com
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 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 ` 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 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 ` Todd Whitesel [this message]
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 Andris Pavenis
1999-03-11 0:27 ` libgdb.a Andris Pavenis
1999-04-01 0:00 ` libgdb.a Andrew Cagney
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=199903110056.QAA00306@alabama.wrs.com \
--to=toddpw@wrs.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