Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Improve i386 prologue analyzer
Date: Thu, 12 Aug 2004 21:41:00 -0000	[thread overview]
Message-ID: <411BE3CB.3020308@gnu.org> (raw)
In-Reply-To: <2914-Thu12Aug2004215629+0300-eliz@gnu.org>


>>>> > And I still don't understand what is the rush to release the MIPS
>>>> > patch without waiting for another week or two and then releasing the
>>>> > i386 patch as well.
>>
>>> 
>>> If I were a MIPS user (hmm, I'm even the maintainer), I'd be pretty 
>>> cheesed off that a fix to get `break main; run' working was being held 
>>> back due the inistance that it be bundled with an unrelated i386 fix.
> 
> 
> Sorry, Andrew, this is just reiterating what I already said I didn't
> understand: if we care so much for the MIPS, why did you refuse to
> wait for it to be fixed in 6.2?

I think I answered this:
> The MIPS breakage wasn't important enough to deny our mainline users a new release of GDB.  Especially when it fixed so many bugs, and especially when the delay could easily be a month..

I've since spoken to some i386 users that benefited from the fixes, they 
are most pleased - threading debugging is way better - dwarf2 back 
traces are much better.  They clearly benefited from pushing forward 
with the 6.2 release.  Only thing is, they are now asking if we can fix 
.... :-)

> And if 6.2 could hit the street with
> MIPS broken, why cannot it stay broken for a week or two more, instead
> of letting the i386 remain broken longer?

And I also think I've covered this:
> However, now that we've got the MIPS patched up, I see no good reason for holding it back.

It's no significant work on my part, and provides us with the 
satisfaction of delivering a better GDB (for MIPS users) sooner.  I'm 
sure the MIPS users would have appreciated the kind gesture.

Andrew



  reply	other threads:[~2004-08-12 21:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 21:58 Mark Kettenis
2004-08-02  4:04 ` Eli Zaretskii
2004-08-02 21:19   ` Andrew Cagney
2004-08-03  3:55     ` Eli Zaretskii
2004-08-06 19:33       ` Mark Kettenis
2004-08-06 20:29         ` Andrew Cagney
2004-08-07 15:37           ` Eli Zaretskii
2004-08-07 16:20             ` Andrew Cagney
2004-08-07 17:11               ` Eli Zaretskii
2004-08-07 17:38                 ` Andrew Cagney
2004-08-07 18:30               ` Joel Brobecker
2004-08-07 18:52                 ` Andrew Cagney
2004-08-07 22:41               ` Michael Chastain
2004-08-08  3:57                 ` Eli Zaretskii
2004-08-08 10:24                   ` Michael Chastain
2004-08-08 11:08                     ` Mark Kettenis
2004-08-08 14:08                       ` Andrew Cagney
2004-08-08 15:04                         ` Mark Kettenis
2004-08-08 19:32                         ` Eli Zaretskii
2004-08-09 13:59                           ` Andrew Cagney
2004-08-09 15:07                             ` Mark Kettenis
2004-08-09 16:46                             ` Michael Chastain
2004-08-09 19:09                             ` Eli Zaretskii
2004-08-11  0:02                               ` Andrew Cagney
2004-08-11  3:53                                 ` Eli Zaretskii
2004-08-11 17:13                                   ` Andrew Cagney
2004-08-11 17:55                                     ` Eli Zaretskii
2004-08-12 12:43                                       ` Andrew Cagney
2004-08-12 19:00                                         ` Eli Zaretskii
2004-08-12 21:41                                           ` Andrew Cagney [this message]
2004-08-08 19:29                       ` Eli Zaretskii
2004-08-08 19:28                     ` Eli Zaretskii
2004-08-07 15:31         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18  9:42 Michael Elizabeth Chastain
2003-08-18 17:17 ` Mark Kettenis
2003-08-17 23:34 Michael Elizabeth Chastain
2003-08-17 23:16 Mark Kettenis

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=411BE3CB.3020308@gnu.org \
    --to=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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