From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com, ezannoni@redhat.com, rth@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] OSF/1 - "next" over prologueless function call
Date: Tue, 02 Dec 2003 07:53:00 -0000 [thread overview]
Message-ID: <20031202075327.4BD444B359@berman.michael-chastain.com> (raw)
Hi Joel,
> ... I see some target-specific code uses a grab-bag field of the
> minimal_symbol structure to store some target-specific information
> (field "info"). I don't particularly fancy typeless fields like this,
> but, just thinking aloud, we could add a new fields holding some flags
> which would be defined in gdb in an manor independent of the target.
I would like to clean up the "info" field.
The only thing it's used for is these target-specific bit flags.
It's really stupid that it's a "void *"!
http://sources.redhat.com/ml/gdb/2003-11/msg00094.html
When I get some more cycles, and Elena gets some more cycles,
I'll bring it up for discussion again.
Michael C
too tired to work, not too tired to blabber
next reply other threads:[~2003-12-02 7:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 7:53 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 5:49 Michael Elizabeth Chastain
2003-12-02 4:26 Joel Brobecker
2003-12-02 4:30 ` Daniel Jacobowitz
2003-12-02 6:06 ` Joel Brobecker
2003-12-02 6:35 ` Richard Henderson
2003-12-02 7:21 ` Joel Brobecker
2003-12-02 15:14 ` Daniel Jacobowitz
2003-12-03 1:54 ` Joel Brobecker
2003-12-02 13:55 ` Daniel Jacobowitz
2003-12-03 4:19 ` Andrew Cagney
2003-12-04 0:55 ` Joel Brobecker
2003-12-04 1:49 ` Andrew Cagney
2003-12-04 23:24 ` Joel Brobecker
2003-12-04 23:28 ` Daniel Jacobowitz
2003-12-05 20:19 ` Andrew Cagney
2003-12-08 23:25 ` Joel Brobecker
2003-12-09 23:10 ` Andrew Cagney
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=20031202075327.4BD444B359@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@redhat.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