Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: * solib-svr4.c (bfd_lookup_symbol): New SECT_FLAGS argument.
Date: Tue, 26 Aug 2003 21:34:00 -0000	[thread overview]
Message-ID: <3F4BD27C.9080502@redhat.com> (raw)

Jim,

What was the final out come of this patch?

2003-06-11  Jim Blandy  <jimb@redhat.com>
        * solib-svr4.c (bfd_lookup_symbol): New SECT_FLAGS argument.
        (enable_break): Pass SEC_CODE as the SECT_FLAGS argument to
        bfd_lookup_symbol, since we only want symbols in code sections.
        (look_for_base): Pass zero as the SECT_FLAGS argument to
        bfd_lookup_symbol, since we're not concerned about which section
        the symbol is in.

it appears to be approved, but not committed?
http://sources.redhat.com/ml/gdb-patches/2003-06/msg00430.html

Andrew


             reply	other threads:[~2003-08-26 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 21:34 Andrew Cagney [this message]
2003-08-26 22:59 ` Jim Blandy

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=3F4BD27C.9080502@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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