From: Andrew Cagney <ac131313@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>, gdb@sources.redhat.com
Subject: [6] What if EXTRA_FRAME_INFO wasn't required
Date: Fri, 28 Mar 2003 21:34:00 -0000 [thread overview]
Message-ID: <3E84BFD5.3080304@redhat.com> (raw)
Joel,
If the need to convert EXTRA_FRAME_INFO was dropped as a barrier to
having HP/UX multi-arch partial, would anything else be left?
I'm wondering how much further the bar needs to be lowered before HP/UX
accidently falls over the multi-arch requirement [#include vision of
HP/UX trying to play the `the stick game', where the sole objective is
to jump / step / fall / crawl over a stick lying flat on the ground, and
still failing :-]
--
My cunning plan is to, since GDB has had so much significant recent
change, reset slightly peoples expectations for this new release. Even
releases are generally associated with stability problems :-)
Andrew
next reply other threads:[~2003-03-28 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 21:34 Andrew Cagney [this message]
2003-03-28 21:39 ` Joel Brobecker
2003-03-31 0:18 ` Andrew Cagney
2003-03-31 22:32 ` Joel Brobecker
2003-03-31 23:36 ` Andrew Cagney
2003-04-08 22:08 ` Andrew Cagney
2003-04-08 22:17 ` Joel Brobecker
2003-03-31 22:24 ` Joel Brobecker
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=3E84BFD5.3080304@redhat.com \
--to=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).