public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/18027] dwarf2 debug info after rebasing DLLs unusable Date: Fri, 17 Feb 2023 02:15:14 +0000 [thread overview] Message-ID: <bug-18027-4717-UReyA2rxWF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18027-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18027 --- Comment #13 from Tom Tromey <tromey at sourceware dot org> --- (In reply to Corinna Vinschen from comment #12) > Isn't there some kind of version information in the DWARF sections somewhere? > GDB could use that to distinguish absolute vs. load-address relative DWARF > info. There is, but it's not useful for this. There's no way to tell which linker was in use. > We have to assume that the DLL has been built with debugging symbols. SO > we can safely assume that the DllMain function is always present. It's not unheard of for programs to have some compilations with debuginfo and some without. I tend to think we'll have to do this the way BFD does: just keep trying symbols until we find one that works. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-17 2:15 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-26 5:36 [Bug win32/18027] New: " corinna at vinschen dot de 2015-02-26 9:39 ` [Bug win32/18027] " asmwarrior at gmail dot com 2023-02-11 17:48 ` tromey at sourceware dot org 2023-02-12 12:20 ` ssbssa at sourceware dot org 2023-02-13 10:31 ` corinna at vinschen dot de 2023-02-13 10:36 ` corinna at vinschen dot de 2023-02-13 14:01 ` simark at simark dot ca 2023-02-13 16:17 ` corinna at vinschen dot de 2023-02-13 17:13 ` simark at simark dot ca 2023-02-13 17:24 ` ssbssa at sourceware dot org 2023-02-13 19:23 ` tromey at sourceware dot org 2023-02-13 19:46 ` ssbssa at sourceware dot org 2023-02-13 19:48 ` corinna at vinschen dot de 2023-02-13 22:08 ` tromey at sourceware dot org 2023-02-15 10:22 ` corinna at vinschen dot de 2023-02-17 2:15 ` tromey at sourceware dot org [this message] 2023-02-28 14:43 ` tromey at sourceware dot org 2023-02-28 15:20 ` corinna at vinschen dot de 2023-02-28 15:22 ` corinna at vinschen dot de 2023-03-24 17:31 ` tromey at sourceware dot org 2023-03-24 19:00 ` corinna at vinschen dot de 2023-03-27 9:19 ` nickc at redhat dot com 2023-03-28 8:58 ` corinna at vinschen dot de 2023-03-28 14:01 ` nickc at redhat dot com 2023-03-28 18:10 ` corinna at vinschen dot de 2023-03-29 12:46 ` tromey at sourceware dot org 2023-03-30 9:23 ` corinna at vinschen dot de 2023-03-30 9:24 ` corinna at vinschen dot de 2023-04-21 16:38 ` tromey at sourceware dot org 2023-04-21 16:54 ` tromey at sourceware dot org 2023-04-21 17:11 ` tromey at sourceware dot org 2023-04-21 19:48 ` corinna at vinschen dot de 2023-04-24 15:54 ` 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-18027-4717-UReyA2rxWF@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).