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/30255] GDB on Windows cannot retrieve a stacktrace when a NULL function pointer is called
Date: Tue, 21 Mar 2023 18:30:32 +0000 [thread overview]
Message-ID: <bug-30255-4717-cRA7QLdOZm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30255-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30255
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom Tromey from comment #3)
> I wonder where the unwound PC comes from.
Probably right there on the stack:
(gdb) x/20xb $sp
0x5ffd68: 0xf1 0x16 0x35 0x8e 0xf7 0x7f 0x00 0x00
(gdb) disassemble $
Dump of assembler code for function a:
0x00007ff78e3516e0 <+0>: push %rbp
0x00007ff78e3516e1 <+1>: mov %rsp,%rbp
0x00007ff78e3516e4 <+4>: sub $0x20,%rsp
0x00007ff78e3516e8 <+8>: mov 0x5951(%rip),%rax #
0x7ff78e357040 <func_ptr>
0x00007ff78e3516ef <+15>: call *%rax
0x00007ff78e3516f1 <+17>: nop
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-21 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 17:30 [Bug gdb/30255] New: " luca.bacci at outlook dot com
2023-03-21 15:46 ` [Bug gdb/30255] " tromey at sourceware dot org
2023-03-21 15:54 ` [Bug win32/30255] " tromey at sourceware dot org
2023-03-21 16:20 ` tromey at sourceware dot org
2023-03-21 18:30 ` tromey at sourceware dot org [this message]
2023-03-21 19:43 ` tromey at sourceware dot org
2023-03-21 20:22 ` luca.bacci at outlook dot com
2023-04-10 14:41 ` cvs-commit at gcc dot gnu.org
2023-04-10 14:42 ` 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-30255-4717-cRA7QLdOZm@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).