public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "massimiliano.cuoghi at systemceramics dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/28288] GDBserver should hide unreported fork childs from thread lists
Date: Fri, 10 Sep 2021 11:45:11 +0000 [thread overview]
Message-ID: <bug-28288-4717-ryqfC5zzS3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28288-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28288
--- Comment #18 from Massimiliano <massimiliano.cuoghi at systemceramics dot com> ---
(In reply to Simon Marchi from comment #16)
> Ok, I reproduced:
>
> (gdb)
> Continuing.
> [Detaching after fork from child process 2096323]
> [New inferior 2]
> Reading /home/simark/Downloads/testcasenew/testcase from remote target...
> Reading /home/simark/Downloads/testcasenew/testcase from remote target...
> Reading symbols from target:/home/simark/Downloads/testcasenew/testcase...
> [New Thread 2096324.2096324]
> [Switching to Thread 2096324.2096324]
> Remote 'g' packet reply is too long (expected 560 bytes, got 816 bytes):
> 000000000000000000000000000000008d315df7ff7f00004075e7f3ff7f00000000000000000
> 0001110000000000000004a00e4ff7f00003875e7f3ff7f00000000000000000000d075e7f3ff
> 7f0000000000000000000046020000000000000100000000000000cc75e7f3ff7f00000000000
> 000000000104e00e4ff7f00008d315df7ff7f000046020000330000002b000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 000000000000000000000000007f03000000000000ffff0000000000000000000000000000000
> 00000000000002f7573722f62696e2f77686f616d69002f7573722f62696e2f77686f616d6900
> 2f002f002f002f002f002f002f002f002f002f000000000000000000000000002929292929292
> 92929292929292929291026d3f7ff7f00000026d3f7ff7f000004000000140100000000000000
> 00000000000000000000000000000000000000697465282900315f715f7374617274750000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 000000000000000000000000000000000000000000000000000000000000000801f0000380000
> 00000000004086e7f3ff7f0000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000
> 000000000000000
>
> I have seen this issue, I have a patch that fixes at least part of that, but
> I did not have time to test it properly and submit it. It is here for now:
>
> https://review.lttng.org/c/binutils-gdb/+/6187
I'm testing the change at the moment it seems to work much better
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-10 11:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:01 [Bug breakpoints/28288] New: gdbserver close connection massimiliano.cuoghi at systemceramics dot com
2021-08-30 15:32 ` [Bug breakpoints/28288] " simark at simark dot ca
2021-08-31 6:44 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:10 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:20 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:23 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:24 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:25 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 9:01 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 13:37 ` simark at simark dot ca
2021-08-31 13:39 ` simark at simark dot ca
2021-09-01 13:38 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:40 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:40 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:45 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 14:12 ` massimiliano.cuoghi at systemceramics dot com
2021-09-10 4:10 ` simark at simark dot ca
2021-09-10 4:10 ` [Bug breakpoints/28288] GDBserver should hide unreported fork childs from thread lists simark at simark dot ca
2021-09-10 4:12 ` simark at simark dot ca
2021-09-10 11:45 ` massimiliano.cuoghi at systemceramics dot com [this message]
2021-09-10 14:20 ` simark at simark dot ca
2021-10-29 9:22 ` massimiliano.cuoghi at systemceramics dot com
2021-10-29 12:03 ` simark at simark dot ca
2021-11-05 12:59 ` massimiliano.cuoghi at systemceramics dot com
2021-11-05 14:39 ` simark at simark dot ca
2021-11-05 14:39 ` simark at simark dot ca
2021-11-08 16:22 ` massimiliano.cuoghi at systemceramics dot com
2021-11-08 16:34 ` simark at simark dot ca
2021-11-11 8:21 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 8:26 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 8:28 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 19:06 ` simark at simark dot ca
2021-11-11 19:13 ` simark at simark dot ca
2021-11-12 10:29 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:29 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:30 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:31 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:31 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:32 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:34 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 13:07 ` simark at simark dot ca
2021-11-12 14:36 ` massimiliano.cuoghi at systemceramics dot com
2021-11-15 7:30 ` massimiliano.cuoghi at systemceramics dot com
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-28288-4717-ryqfC5zzS3@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).