public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: eliz@elta.co.il
Cc: gdb@sources.redhat.com
Subject: Re: [HEADS UP] Merging i386newframe into mailine
Date: Sat, 24 May 2003 11:27:00 -0000	[thread overview]
Message-ID: <200305241127.h4OBR6YX025477@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <6480-Sat24May2003125340+0300-eliz@elta.co.il>

   Date: Sat, 24 May 2003 12:53:42 +0300
   From: "Eli Zaretskii" <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?

AFAICT DJGPP should be fine.  The default debugging format for DJGPP
is still SDB isn't it?  In that case the new DWARF CFI unwinder
wouldn't be used, unless DWARF2 EH info is generated.

The GCC config files seems to suggest that DJGPP also supports DWARF2.
If that indeed works, compiling with -gdwarf-2 would make the DWARF
CFI support kick in.

   > 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.

But for some, DWARF CFI support will be a valuable fix :-).

   So how about waiting for 6.1 with the merge?

Hmm, having stuff slightly broken in 6.0 might be more acceptable to
our users than breaking things in 6.1.

  reply	other threads:[~2003-05-24 11:27 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 [this message]
2003-05-24 17:38     ` Eli Zaretskii
2003-05-26 15:31   ` Andrew Cagney
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=200305241127.h4OBR6YX025477@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=eliz@elta.co.il \
    --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).