From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Reporting the STATUS_INVALID_UNWIND_TARGET fatal error
Date: Tue, 07 Oct 2014 17:49:00 -0000 [thread overview]
Message-ID: <543427A0.5040708@redhat.com> (raw)
In-Reply-To: <83iojvlrkn.fsf@gnu.org>
On 10/07/2014 06:26 PM, Eli Zaretskii wrote:
>> Date: Tue, 07 Oct 2014 18:01:47 +0100
>> From: Pedro Alves <palves@redhat.com>
>>
>> On 09/30/2014 06:54 PM, Eli Zaretskii wrote:
>>> In the native MinGW build of GDB, we currently do not interpret
>>> STATUS_INVALID_UNWIND_TARGET, neither as a Posix-style signal nor as a
>>> Windows exception (under debugexceptions). As result, GDB says
>>> something like
>>>
>>> gdb: unknown target exception 0xc0000029 at 0x7c9502cc
>>>
>>> Would it make sense to report this as SIGSEGV instead?
>>
>> Doesn't sound like segmentation fault, but rather the
>> runtime detecting some corruption.
>
> But stack-related trouble, like stack overflows, are reported as
> segfaults, right?
Only if they really cause a segmentation fault. Reusing the stack
of another thread would not, as that stack would be mapped in to
the process.
>
>> Like, e.g., glibc's malloc/free detecting a heap corruption and
>> printing about that.
>
> It's not a case of corruption. Nothing is wrong with the stack per
> se. In addition, it's a true exception, not a debugging feature
> provided by some library. So I think it's different.
>
>>> This happens, e.g., when a thread tries to longjmp using stack
>>> information recorded by a different thread. What will GDB report in
>>> such a case on GNU/Linux or other Posix platforms?
>>
>> I think nothing.
>
> Could you or someone else try?
>
>> In absence of a more specific signal, I think SIGTRAP is the
>> best match, for being a "debugger" signal. This has the advantage
>> that SIGTRAP is not passed to the program by default, so a plain
>> "continue" should suppress the exception, while "signal SIGTRAP"
>> will pass it to the program (which I guess will usually terminate
>> the application).
>
> You cannot continue from this exception, not on Windows anyway. Your
> program dies.
>
>> Though overall, I think it'd be better if we added a new
>> "target exception" waitkind or some such, and stopped trying
>> to masquerade Windows exceptions as Unix signals.
>
> What would it take to do something like that?
I'd try adding a new TARGET_WAITKIND_EXCEPTION, and have windows-nat.c
report that, putting the exception number in waitstatus.value.integer.
In handle_inferior_event, you'd handle it probably similarly to
TARGET_WAITKIND_NO_HISTORY, by reporting the exception and causing
a stop. To interpret the exception number, and say, convert it to
a printable string, you'd add a new gdbarch hook, that'd be
implemented in windows-tdep.c. To make the contents of the whole exception
object available to GDB and the user, I'd try adding a new convenience
variable, similar to $_siginfo or $_tlb. See windows-tdep.c for
the latter.
Thanks,
Pedro Alves
prev parent reply other threads:[~2014-10-07 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:54 Eli Zaretskii
2014-10-07 17:01 ` Pedro Alves
2014-10-07 17:25 ` Eli Zaretskii
2014-10-07 17:49 ` Pedro Alves [this message]
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=543427A0.5040708@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@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).