public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17659] [win32] GDB failed to get dll names when handling LOAD_DLL_DEBUG_EVENT event Date: Mon, 05 Apr 2021 17:41:12 +0000 [thread overview] Message-ID: <bug-17659-4717-ecMN63t34c@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17659-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17659 Eli Zaretskii <eliz at gnu dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |eliz at gnu dot org Resolution|FIXED |--- --- Comment #5 from Eli Zaretskii <eliz at gnu dot org> --- I'm reopening this. The problem is not completely solved, because the changes pointed to in Comment 3 only handle the DLLs loaded at program start. They don't handle the same problem with DLLs that are dynamically loaded by the debuggee at run time. This is exactly what happens in Emacs with native-compilation of Lisp packages. Each Lisp package is compiled into one or more *.eln files, each of which is a DLL in disguise. Emacs loads each of these *.eln files when it needs it the first time. Some of those DLLs appear to GDB with NULL or empty name as found by following the lpImageName member of the DLL debug event, and then GDB doesn't know about these DLLs, and cannot produce valid backtraces and other debug support for those DLLs. To fix that we need either the code shown by asmwarrior, or another call to windows_add_all_dlls, either automatically upon receiving a DLL load debug event for which we are unable to glean the DLL name, or at least manually whenever a loaded DLL doesn't appear in "info shared". See also my report of the results of this problem in https://sourceware.org/pipermail/gdb-patches/2021-March/176909.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-05 17:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-28 1:10 [Bug gdb/17659] New: " asmwarrior at gmail dot com 2021-04-05 17:41 ` eliz at gnu dot org [this message] 2021-04-06 15:22 ` [Bug gdb/17659] " eliz at gnu dot org 2021-04-06 15:24 ` eliz at gnu dot org 2021-04-10 8:47 ` eliz at gnu 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-17659-4717-ecMN63t34c@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).