public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/18749] problems if whole process dies while (ptrace-) stopped Date: Fri, 31 Jul 2015 11:18:00 -0000 [thread overview] Message-ID: <bug-18749-4717-GPpwFqMU2x@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18749-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18749 --- Comment #1 from Pedro Alves <palves at redhat dot com> --- I'm adding a test to the testsuite that exposes several of these on at least native GNU/Linux: E.g., on one run: [Thread 0x7ffff6fbe700 (LWP 1332) exited] Cannot access memory at address 0x400872 And on another: [Thread 0x7ffff3fb8700 (LWP 2161) exited] Cannot find user-level thread for LWP 2163: generic error (gdb) [Thread 0x7ffff2fb6700 (LWP 2163) exited] [Thread 0x7ffff47b9700 (LWP 2160) exited] -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-31 11:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-31 11:18 [Bug gdb/18749] New: " palves at redhat dot com 2015-07-31 11:18 ` palves at redhat dot com [this message] 2015-08-21 19:13 ` [Bug gdb/18749] " cvs-commit at gcc dot gnu.org 2024-01-03 14:49 ` ssbssa 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-18749-4717-GPpwFqMU2x@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).