From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: kettenis@chello.nl, gdb@sources.redhat.com
Subject: Re: [HEADS UP] Merging i386newframe into mailine
Date: Mon, 26 May 2003 15:31:00 -0000 [thread overview]
Message-ID: <3ED232A1.2090407@redhat.com> (raw)
In-Reply-To: <6480-Sat24May2003125340+0300-eliz@elta.co.il>
>> Date: Fri, 23 May 2003 18:52:54 +0200 (CEST)
>> From: Mark Kettenis <kettenis@chello.nl>
>>
>> * Possibly breaking a few unmaintained i386 targets.
>
>
> Could the DJGPP (a.k.a. go32) target be one of those?
>
>
>> I think it's worth running these risks, especially since recent
>> devlopments on Linux/i386 demand DWARF CFI support on the i386.
>
>
> OTOH, GDB 6 will have many valuable fixes, and it would be a pity to
> deny those features from users of platforms that could be broken by
> the merge.
>
> So how about waiting for 6.1 with the merge?
(mark, correct?)
I believe any potential i386 problems should be confined to things like
signal handlers (unwinding through, or from them).
Basic break-main;run functionality should be fine (in fact slightly
better because the non CFI unwinder was also improved).
Andrw
next prev parent reply other threads:[~2003-05-26 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 16:52 Mark Kettenis
2003-05-23 17:15 ` Andrew Cagney
2003-05-24 9:52 ` Eli Zaretskii
2003-05-24 11:27 ` Mark Kettenis
2003-05-24 17:38 ` Eli Zaretskii
2003-05-26 15:31 ` Andrew Cagney [this message]
2003-05-29 15:14 ` Mark Kettenis
2003-05-29 16:48 ` Andrew Cagney
[not found] ` <200305231745.h4NHj2JL029521@gremlin.ics.uci.edu>
2003-05-24 11:15 ` 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=3ED232A1.2090407@redhat.com \
--to=ac131313@redhat.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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).