| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
| From: | =?ISO-8859-1?Q?Hans-Bernhard_Br=F6ker?= <HBBroeker AT t-online DOT de> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Abort when compiling using COFF debug format (-gcoff) |
| Date: | Sun, 29 Jan 2012 20:45:35 +0100 |
| Lines: | 21 |
| Message-ID: | <9ollutFfvsU1@mid.dfncis.de> |
| References: | <201201262112 DOT 52030 DOT juan DOT guerrero AT gmx DOT de> <83wr8eywzf DOT fsf AT gnu DOT org> <4faf5c37-ca50-4bd0-9081-3ada327099a5 AT h6g2000yqk DOT googlegroups DOT com> <83sjj1zlmn DOT fsf AT gnu DOT org> <f29ff743-4470-4cc9-8307-47ee7359dbcf AT b23g2000yqn DOT googlegroups DOT com> <8339b0z1gr DOT fsf AT gnu DOT org> <23088c26-d434-4679-b7dd-fdd5459c9ad4 AT h3g2000yqe DOT googlegroups DOT com> <9olf84Fp8oU1 AT mid DOT dfncis DOT de> <838vkqqs4f DOT fsf AT gnu DOT org> |
| Mime-Version: | 1.0 |
| X-Trace: | news.dfncis.de FzZJMcqgyayNIwa0kvnMxQqtKGz/YZxRF43VlWr0KaFFZfY25L1TShoOWt |
| Cancel-Lock: | sha1:DOzMSXjksdS8NT6P7rN6DaXnFdg= |
| User-Agent: | Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 |
| In-Reply-To: | <838vkqqs4f.fsf@gnu.org> |
| Bytes: | 2079 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On 29.01.2012 19:29, Eli Zaretskii wrote:
>> From: Hans-Bernhard Bröker<HBBroeker AT t-online DOT de>
>> Date: Sun, 29 Jan 2012 18:51:01 +0100
>>
>> On 29.01.2012 14:43, Rugxulo wrote:
>>
>>> Guess so. But I don't see any obvious way to later on tell what
>>> specific debug info was generated at compile time. ("file" apparently
>>> doesn't tell, at least not on .EXEs.)
>>
>> The tool-for-the-task there would be objdump. Particularly the output
>> of the -g, -G and/or -Wi flags.
>
> I tried that before replying, but couldn't find any objdump switch
> which would tell the debug info format.
Those flags do provide that information somewhat indirectly: by printing
nothing if there's nothing to find in the given format (stabs and DWARF,
respectively). -g interprets COFF debug info if present, otherwise it
only prints external symbols.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |