public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug shlibs/7885] Problem to debug a DLL
Date: Fri, 19 Jan 2024 14:04:56 +0000	[thread overview]
Message-ID: <bug-7885-4717-7qbywjwUxy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-7885-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=7885

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |7.5

--- Comment #3 from Hannes Domani <ssbssa at sourceware dot org> ---
Debugging a dll when the main application has no debug symbols works for me
since gdb-7.5:
```
Reading symbols from C:\src\tests\gdb-7885-main.exe...(no debugging symbols
found)...done.
(gdb) b indll
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (indll) pending.
(gdb) r
Starting program: C:\src\tests\gdb-7885-main.exe
[New Thread 8308.0x25f8]

Breakpoint 1, indll (x=12) at gdb-7885-dll.c:4
4         return x + 2;
(gdb) p x
$1 = 12
(gdb) c
Continuing.
indll = 14
[Inferior 1 (process 8308) exited normally]
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2024-01-19 14:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-7885-4717@http.sourceware.org/bugzilla/>]

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-7885-4717-7qbywjwUxy@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: link
Be 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).