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/14018] Win32 fails to continue with "winerr 5" (pc register not available) after SigTrap while process paused Date: Sat, 19 Apr 2014 08:20:00 -0000 [thread overview] Message-ID: <bug-14018-4717-ahNYX0kgRy@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14018-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=14018 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 17617f2d366ca969ccbc784be4f75931a1afd20f (commit) from 5723a6fd0636bed6d278ab19f6ead31d748a7a78 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=17617f2d366ca969ccbc784be4f75931a1afd20f commit 17617f2d366ca969ccbc784be4f75931a1afd20f Author: Eli Zaretskii <eliz@gnu.org> Date: Sat Apr 19 11:12:19 2014 +0300 PR gdb/14018 -- avoid "PC register not available" errors. gdb/windows-nat.c (thread_rec): Don't display a warning when SuspendThread fails with ERROR_ACCESS_DENIED. If SuspendThread fails for any reason, set th->suspended to -1, so that we don't try to resume such a thread. Also, don't return NULL in these cases, to avoid completely ruin the session due to "PC register is not available" error. (do_windows_fetch_inferior_registers): Check errors in GetThreadContext call. (windows_continue): Accept an additional argument KILLED; if not zero, ignore errors in the SetThreadContext call, since the inferior was killed and is shutting down. (windows_resume, get_windows_debug_event) (windows_create_inferior, windows_mourn_inferior) (windows_kill_inferior): All callers of windows_continue changed to adjust to its new calling sequence. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 19 +++++++++++++++++++ gdb/windows-nat.c | 49 +++++++++++++++++++++++++++++++++---------------- 2 files changed, 52 insertions(+), 16 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-19 8:20 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-24 22:45 [Bug gdb/14018] New: " gdb.bugs at mfriebe dot de 2012-04-28 14:02 ` [Bug win32/14018] " gdb.bugs at mfriebe dot de 2012-11-01 14:39 ` andre.poenitz at digia dot com 2013-09-09 13:27 ` orgads at gmail dot com 2013-11-21 14:35 ` david.schulz at digia dot com 2013-11-21 14:49 ` brobecker at gnat dot com 2014-04-19 8:20 ` cvs-commit at gcc dot gnu.org [this message] 2014-04-19 8:27 ` cvs-commit at gcc dot gnu.org 2014-04-21 15:40 ` brobecker at gnat dot com 2014-05-05 21:54 ` cvs-commit at gcc dot gnu.org 2021-09-22 16:58 ` mervegunesli at aol dot com 2021-09-22 17:04 ` mark at klomp 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-14018-4717-ahNYX0kgRy@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: 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).