From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26323 invoked by alias); 24 May 2003 11:27:11 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26269 invoked from network); 24 May 2003 11:27:10 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (62.163.169.212) by sources.redhat.com with SMTP; 24 May 2003 11:27:10 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h4OBR62H000477; Sat, 24 May 2003 13:27:06 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h4OBR7Aw025480; Sat, 24 May 2003 13:27:07 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h4OBR6YX025477; Sat, 24 May 2003 13:27:06 +0200 (CEST) Date: Sat, 24 May 2003 11:27:00 -0000 Message-Id: <200305241127.h4OBR6YX025477@elgar.kettenis.dyndns.org> From: Mark Kettenis To: eliz@elta.co.il CC: gdb@sources.redhat.com In-reply-to: <6480-Sat24May2003125340+0300-eliz@elta.co.il> Subject: Re: [HEADS UP] Merging i386newframe into mailine References: <200305231652.h4NGqs4Y023667@elgar.kettenis.dyndns.org> <6480-Sat24May2003125340+0300-eliz@elta.co.il> X-SW-Source: 2003-05/txt/msg00339.txt.bz2 Date: Sat, 24 May 2003 12:53:42 +0300 From: "Eli Zaretskii" > Date: Fri, 23 May 2003 18:52:54 +0200 (CEST) > From: Mark Kettenis > > * 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.