public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/28065] FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem (print global_var after writing again, inf=1, iter=354)
Date: Thu, 08 Jul 2021 11:23:43 +0000 [thread overview]
Message-ID: <bug-28065-4717-tcDyug0XXC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28065-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28065
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 13546
--> https://sourceware.org/bugzilla/attachment.cgi?id=13546&action=edit
debug patch
(In reply to Pedro Alves from comment #4)
> Could it be that opening /proc/pid/task/lwp/mem is failing with errno other
> than EACCES or ENOENT on openSUSE's kernel?
>
> To debug this, I'd insert abort() calls in all TARGET_XFER_EOF failure paths
> in linux_proc_xfer_memory_partial, and then set the testcase running in a
> loop. Then debug the core dump.
Core dump gives this location:
...
(gdb) up
#6 0x0000000000801ec9 in linux_proc_xfer_memory_partial (readbuf=0x2dc7620 "",
writebuf=0x0, offset=6295664, len=4, xfered_len=0x7ffc589ada38)
at /home/vries/gdb_versions/devel/src/gdb/linux-nat.c:4007
4007 gdb_assert_not_reached ("4");
(gdb) l
4002
4003 if (res == 0)
4004 {
4005 /* EOF means the address space is gone, the whole process
4006 exited or execed. */
4007 gdb_assert_not_reached ("4");
4008 return TARGET_XFER_EOF;
4009 }
4010 else if (res == -1)
4011 {
(gdb)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-08 11:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 9:57 [Bug threads/28065] New: " vries at gcc dot gnu.org
2021-07-08 10:01 ` [Bug threads/28065] " vries at gcc dot gnu.org
2021-07-08 10:01 ` vries at gcc dot gnu.org
2021-07-08 10:06 ` vries at gcc dot gnu.org
2021-07-08 10:41 ` vries at gcc dot gnu.org
2021-07-08 10:41 ` vries at gcc dot gnu.org
2021-07-08 10:45 ` pedro at palves dot net
2021-07-08 11:03 ` vries at gcc dot gnu.org
2021-07-08 11:23 ` vries at gcc dot gnu.org [this message]
2021-07-08 12:06 ` pedro at palves dot net
2021-07-08 13:20 ` vries at gcc dot gnu.org
2021-07-08 13:34 ` pedro at palves dot net
2021-07-09 9:41 ` vries at gcc dot gnu.org
2021-07-09 9:44 ` vries at gcc dot gnu.org
2021-07-09 13:33 ` vries at gcc dot gnu.org
2021-07-09 16:19 ` vries at gcc dot gnu.org
2021-07-09 16:40 ` pedro at palves dot net
2021-07-09 17:11 ` pedro at palves dot net
2021-07-09 18:57 ` vries at gcc dot gnu.org
2021-07-09 19:06 ` pedro at palves dot net
2021-07-09 19:10 ` pedro at palves dot net
2021-07-09 20:32 ` pedro at palves dot net
2021-07-09 21:53 ` vries at gcc dot gnu.org
2021-07-09 22:55 ` pedro at palves dot net
2021-07-10 12:24 ` simark at simark dot ca
2021-10-05 11:27 ` vries at gcc dot gnu.org
2021-11-05 17:58 ` cvs-commit at gcc dot gnu.org
2021-11-05 18:02 ` pedro at palves dot net
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-28065-4717-tcDyug0XXC@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).