DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 609HPvB12577466
Authentication-Results:	delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=delorie.com
X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 609HPvSC2577429
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=polymtl.ca
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=polymtl.ca
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 609HPvSC2577429
Authentication-Results:	delorie.com;
	dkim=pass (2048-bit key, unprotected) header.d=polymtl.ca header.i=@polymtl.ca header.a=rsa-sha256 header.s=oct2025 header.b=rWVIyf4z
X-Recipient:	djgpp AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 smtp.polymtl.ca 609HPpq3175176
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=polymtl.ca;
	s=oct2025; t=1767979556;
	bh=3a70T8PNoWrPW/L1cUntUyxwUrdZvvdCHta2zF13Oto=;
	h=Date:From:Subject:To:From;
	b=rWVIyf4zfsqK3wF7x62adZG6masHN/6u0GAT9sc92BIxSqqlRmygg/4h8f43ETBwR
	bHzDxJOy3rFI4q4EbFMnj0lxt+9xw7qJ3SaPdcKeefWiRG+u+gGLsuf8iR1Dd0wcB5
	0yW4E042FmMxd9uuYXd/ChH4g3hInI+5LG7T0PTFqEheqqK2Zi6D4HeOR0nx//2cjS
	o+KHH70xVdOgKdqWNidPZK9Y4sWeSz5ZJm6zBW+FX9Sp4FguxFE6WB0ZYt6McTCm6O
	hUsWmaWCqQmycbqpEdC5zLEkBIufvMOwI6vcbB2h1sTlEIBldaHzGZG98dNAZHYdLr
	5+x+cMAGh3vVw==
Message-ID:	<0752ebcc-24dd-4ea1-ad68-7822463d0eda@polymtl.ca>
Date:	Fri, 9 Jan 2026 12:25:50 -0500
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
From:	"Simon Marchi (simon DOT marchi AT polymtl DOT ca) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Subject:	Supported debug info formats
To:	djgpp AT delorie DOT com
X-Poly-FromMTA:	(simark.ca [158.69.221.121]) at Fri, 9 Jan 2026 17:25:51 +0000
Reply-To:	djgpp AT delorie DOT com

Hi,

GDB maintainer here.  I'm in the process of cleaning up obsolete things,
like debug info formats that are not longer relevant.  I am now looking
at COFF [1].  I am wondering if this is still useful for DJGPP, or if
nowadays you can use DWARF like most other targets (or if people use GDB
for DJGPP at all).

In the gcc source code [1] I see this, so I guess that DWARF 2 is the
default debug format now?

    /* Support generation of DWARF2 debugging info.  */
    #define DWARF2_DEBUGGING_INFO 1

    #undef PREFERRED_DEBUGGING_TYPE
    #define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG

...

        /* Don't emit DWARF3/4 unless specifically selected. */         \
        /* DWARF3/4 currently does not work for DJGPP.  */              \
        if (!OPTION_SET_P (dwarf_version))                        \
            dwarf_version = 2;                                          \
                                                                        \
        }                                                               \

Note that I am only talking about the debug info aspects of COFF,
there are probably some things in coffread.c that would still be needed
in order to read executable files on Windows and/or DJGPP.

Thanks,

Simon

[1] https://gitlab.com/gnutools/gcc/-/blob/c10076b34d3ede485bfb306b2a91feeee8368cd5/gcc/config/i386/djgpp.h#L20-24

- Raw text -