From: Thomas Schwinge <thomas@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/gdbserver] Unexpected EOF read from socket after inferior exits.
Date: Wed, 21 Jul 2010 20:49:00 -0000 [thread overview]
Message-ID: <87fwzcftml.fsf@dirichlet.schwinge.homeip.net> (raw)
In-Reply-To: <87mxtlkgac.fsf@dirichlet.schwinge.homeip.net> (Thomas Schwinge's message of "Tue, 20 Jul 2010 23:13:47 +0200")
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
Hello!
On 2010-07-20 21:13, I wrote:
> Running /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/testsuite/gdb.threads/current-lwp-dead.exp ...
> [...]
> > 'LD_LIBRARY_PATH=[...] [ld.so] [gdbserver] ':2887' 'current-lwp-dead'
> Process current-lwp-dead created; pid = 20009
> Listening on port 2887
> target remote philidor:2887
> Remote debugging using philidor:2887
> Remote debugging from host 10.0.0.218
> [...]
> Breakpoint 2, fn_return (unused=0x0) at /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/testsuite/gdb.threads/current-lwp-dead.c:45
> 45 return 0; /* at-fn_return */
> (gdb) PASS: gdb.threads/current-lwp-dead.exp: continue to breakpoint: fn_return
> testcase /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/testsuite/gdb.threads/current-lwp-dead.exp completed in 2 seconds
> Running /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/testsuite/gdb.threads/execl.exp ...
>
> Here this test has finished, the remote gdbserver terminates, and the
> next test is about to be started.
>
> Executing on host: mips64el-linux-gnu-gcc /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/testsuite/gdb.threads/execl.c [...]
> Killing all inferiors
> Segmentation fault
>
> Instead of terminating, the remote gdbserver crashed with a segfault.
>
> (gdb) bt
> #0 0x1003b068 in thread_db_mourn (proc=0x0) at /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/gdbserver/thread-db.c:889
> #1 0x1002bc3c in linux_mourn (process=0x0) at /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/gdbserver/linux-low.c:896
> #2 0x1001085c in handle_v_cont (own_buf=0x555800d0 "W00") at /scratch/thomas/issue8927-FM_mips64el-linux-gnu/src/gdb-mainline/gdb/gdbserver/server.c:1785
I'm testing a patch for gdbserver.
Regards,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-07-21 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:30 Joel Brobecker
2010-07-06 22:30 ` Daniel Jacobowitz
2010-07-07 16:10 ` Joel Brobecker
2010-07-20 21:14 ` Thomas Schwinge
2010-07-21 20:49 ` Thomas Schwinge [this message]
2010-08-11 12:16 ` Thomas Schwinge
2010-08-11 13:22 ` Pedro Alves
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=87fwzcftml.fsf@dirichlet.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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