From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, jason-swarelist@molenda.com
Cc: dan@cgsoftware.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] bug in symtab.c:lookup_block_symbol()'s search method
Date: Mon, 17 Sep 2001 22:56:00 -0000 [thread overview]
Message-ID: <3BA6E214.9020700@cygnus.com> (raw)
In-Reply-To: <200109160715.JAA07114@is.elta.co.il>
>> Date: Sat, 15 Sep 2001 14:02:35 -0700
>> From: Jason Molenda <jason-swarelist@molenda.com>
>>
>> I'd like to stay focused on the topic on hand for now. This
>> discussion is about gdb currently experiencing a serious performance
>> regression wrt the last release of gdb, and I'm submitting a patch
>> to fix that. I'd like to see this problem addressed before 5.1 goes
>> out.
>
>
> Why do you think it needs to be addressed in 5.1? AFAIK, the fact
> that the release branch was cut means that only relatively safe
> bugfixes are accepted on the branch. This change doesn't seem safe
> enough IMHO, since we still continue arguing whether there are or
> aren't cases where Dan's change matters.
The suggested criteria for committing something to the 5.1 branch are:
o does it build (and if not did it build in 5.0/4.18)
o does ``break main; run'' work
Jason, you've indicate that this seriously hurts Apple's GDB branch.
Since (FSF) GDB has never worked on MacOS X, I don't think hurting
Apple's GDB branch is really qualifies as a reason for getting something
into 5.1 of GDB (The trunk yes definitly, just not the branch).
The reason 5.1 has got hung up is because people have found platforms
that suffered more basic bit rot :-(
Andrew
next prev parent reply other threads:[~2001-09-17 22:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 7:48 Jason Molenda
2001-09-10 11:24 ` Michael Snyder
2001-09-10 11:32 ` Jason Molenda
2001-09-10 11:50 ` Daniel Berlin
2001-09-10 11:52 ` Daniel Berlin
[not found] ` <20010910130347.A5628@shell17.ba.best.com>
2001-09-10 14:17 ` Daniel Berlin
2001-09-14 7:53 ` Andrew Cagney
2001-09-14 8:53 ` Daniel Berlin
2001-09-14 9:06 ` Eli Zaretskii
2001-09-14 9:13 ` Jason Molenda
2001-09-14 9:58 ` Daniel Berlin
2001-09-14 10:55 ` Eli Zaretskii
2001-09-14 10:52 ` Eli Zaretskii
2001-09-14 10:59 ` Daniel Jacobowitz
2001-09-14 11:57 ` Eli Zaretskii
2001-09-15 0:54 ` Jason Molenda
2001-09-15 3:43 ` Eli Zaretskii
2001-09-15 8:01 ` Daniel Berlin
2001-09-15 9:09 ` Eli Zaretskii
2001-09-15 12:36 ` Daniel Jacobowitz
2001-09-15 12:52 ` Jason Molenda
2001-09-15 7:54 ` Daniel Berlin
2001-09-15 13:08 ` Jason Molenda
2001-09-15 13:33 ` Daniel Berlin
2001-09-15 13:52 ` Daniel Berlin
2001-09-15 14:02 ` Jason Molenda
2001-09-15 14:21 ` Daniel Berlin
2001-09-16 0:15 ` Eli Zaretskii
2001-09-17 22:56 ` Andrew Cagney [this message]
2001-09-17 23:12 ` Jason Molenda
2001-09-18 6:21 ` Daniel Berlin
2001-09-18 7:32 ` Andrew Cagney
2001-09-17 23:18 ` Daniel Jacobowitz
2001-09-18 4:51 ` Eli Zaretskii
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=3BA6E214.9020700@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dan@cgsoftware.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jason-swarelist@molenda.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