public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Add WOW64 exception numbers to $_siginfo.ExceptionCode enum Date: Fri, 24 Apr 2020 16:57:29 +0000 (GMT) [thread overview] Message-ID: <20200424165729.114C7386EC42@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9852ceef7f07b60a757870bafcf044e7d93e08ed commit 9852ceef7f07b60a757870bafcf044e7d93e08ed Author: Hannes Domani <ssbssa@yahoo.de> Date: Fri Apr 24 17:12:48 2020 +0200 Add WOW64 exception numbers to $_siginfo.ExceptionCode enum gdb/ChangeLog: 2020-04-24 Hannes Domani <ssbssa@yahoo.de> * windows-tdep.c (exception_values): Add WOW64 exception numbers. Diff: --- gdb/ChangeLog | 4 ++++ gdb/windows-tdep.c | 2 ++ 2 files changed, 6 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 7d34d43a578..4b909b8c94f 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2020-04-24 Hannes Domani <ssbssa@yahoo.de> + + * windows-tdep.c (exception_values): Add WOW64 exception numbers. + 2020-04-24 Kamil Rytarowski <n54@gmx.com> * inf-ptrace.h (follow_fork, insert_fork_catchpoint) diff --git a/gdb/windows-tdep.c b/gdb/windows-tdep.c index 153ad132b96..7772df4c287 100644 --- a/gdb/windows-tdep.c +++ b/gdb/windows-tdep.c @@ -768,6 +768,8 @@ create_enum (struct gdbarch *gdbarch, int bit, const char *name, static const struct enum_value_name exception_values[] = { { 0x40000015, "FATAL_APP_EXIT" }, + { 0x4000001E, "WX86_SINGLE_STEP" }, + { 0x4000001F, "WX86_BREAKPOINT" }, { 0x40010005, "DBG_CONTROL_C" }, { 0x40010008, "DBG_CONTROL_BREAK" }, { 0x80000002, "DATATYPE_MISALIGNMENT" },
reply other threads:[~2020-04-24 16:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200424165729.114C7386EC42@sourceware.org \ --to=ssbssa@sourceware.org \ --cc=gdb-cvs@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).