This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [HEADS UP] Merging i386newframe into mailine

From: Andrew Cagney <ac131313 at redhat dot com>
To: Eli Zaretskii <eliz at elta dot co dot il>
Cc: kettenis at chello dot nl, gdb at sources dot redhat dot com
Date: Mon, 26 May 2003 11:28:33 -0400
Subject: Re: [HEADS UP] Merging i386newframe into mailine
References: <200305231652.h4NGqs4Y023667@elgar.kettenis.dyndns.org> <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

Follow-Ups:
- Re: [HEADS UP] Merging i386newframe into mailine
  - From: Mark Kettenis

References:
- [HEADS UP] Merging i386newframe into mailine
  - From: Mark Kettenis
- Re: [HEADS UP] Merging i386newframe into mailine
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]