public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.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: Mon, 10 Apr 2023 14:41:47 +0000 [thread overview]
Message-ID: <bug-30255-4717-Llp7WLzEDE@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 #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a0f6c61c9ab998cd77b0899a4bdea9576d6d775f
commit a0f6c61c9ab998cd77b0899a4bdea9576d6d775f
Author: Tom Tromey <tromey@adacore.com>
Date: Tue Mar 21 13:40:03 2023 -0600
Handle unwinding from SEGV on Windows
PR win32/30255 points out that a call to a NULL function pointer will
leave gdb unable to "bt" on Windows.
I tracked this down to the amd64 windows unwinder. If we treat this
scenario as if it were a leaf function, unwinding works fine.
I'm not completely sure this patch is the best way. I considered
having it check for 'pc==0' -- but then I figured this could affect
any inaccessible PC, not just the special 0 value.
No test case because I can't run dejagnu tests on Windows. I tested
this by hand using the test case in the bug.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30255
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-10 14:41 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
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 [this message]
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-Llp7WLzEDE@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).