public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lrn1986 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/14527] New: warning: section .gnu_debuglink not found in MODULENAME.debug Date: Tue, 28 Aug 2012 16:53:00 -0000 [thread overview] Message-ID: <bug-14527-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14527 Bug #: 14527 Summary: warning: section .gnu_debuglink not found in MODULENAME.debug Product: gdb Version: 7.5 Status: NEW Severity: minor Priority: P2 Component: win32 AssignedTo: unassigned@sourceware.org ReportedBy: lrn1986@gmail.com Classification: Unclassified Run this: gcc -g ./test.c -o ./test.exe objcopy --only-keep-debug ./test.exe ./test.exe.dbg objcopy --strip-debug ./test.exe objcopy --add-gnu-debuglink="test.exe.dbg" ./test.exe gdb -ex r -ex q --return-child-result ./test.exe test.c: #include <stdio.h> int main (int argc, char **argv) { printf ("Hello, World!\n"); return 0; } gdb (7.5 from mingw.org) will say: Reading symbols from PATH_TO\test.exe...Reading symbols from PATH_TO\test.exe.dbg... warning: section .gnu_debuglink not found in PATH_TO\test.exe.dbg done. done. Why does gdb warn me about the lack of debuglink in a file with full debug info (the test.exe.dbg file)? It's not supposed to have that section. This can be worked around by doing the following: objcopy --only-keep-debug ./test.exe ./test.exe.dbg objcopy --add-gnu-debuglink="test.exe.dbg" ./test.exe objcopy --only-keep-debug ./test.exe ./test.exe.dbg objcopy --remove-section=.gnu_debuglink ./test.exe objcopy --strip-debug ./test.exe objcopy --add-gnu-debuglink="test.exe.dbg" ./test.exe This way test.exe.gbg file gets a .gnu_debuglink section (doesn't matter where it's pointing), and its contents pass the CRC32 check -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-08-28 16:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-28 16:53 lrn1986 at gmail dot com [this message] 2012-12-19 8:06 ` [Bug win32/14527] " muhammad_bilal at mentor dot com 2012-12-19 10:21 ` lrn1986 at gmail dot com 2013-03-31 1:06 ` lrn1986 at gmail dot com 2013-03-31 2:26 ` lrn1986 at gmail dot com 2013-03-31 2:29 ` mbilal at codesourcery dot com 2014-04-05 6:46 ` asmwarrior at gmail dot com 2023-02-17 16:47 ` tromey at sourceware dot org
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=bug-14527-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).