public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dinc.tarkan at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27627] New: GDB cannot get long threadinfo data over UDP Date: Tue, 23 Mar 2021 08:05:25 +0000 [thread overview] Message-ID: <bug-27627-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27627 Bug ID: 27627 Summary: GDB cannot get long threadinfo data over UDP Product: gdb Version: 9.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dinc.tarkan at gmail dot com Target Milestone: --- I am using remote-target debugging and connected to target over UDP. I have one process and 60 threads and every thread has 30 characters long name and using a non-stop debug. So the thread info xml data is over 1kB. gdb first ask for process info with "qXfer:osdata:read:processes:0,283" Since the data is bigget than 643 (0x283) byte, the answer is "m<osdata type="processes">...". gdb understands the multiple packet format and continues to ask for osdata information "qXfer:osdata:read:processes:283,283" and so on until it receives the package startind with 'l'. Later gdb asks for thread info "qXfer:thread:read::0,44b" and the answer is "m<threads>...." but after that gdb stop asking the remaining thread info. The xml data is incomplete and when it trys to parse the data, gdb terminates due to an error. I changed the connection type to TCP, nothing else changed and it works as expected. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-03-23 8:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 8:05 dinc.tarkan at gmail dot com [this message] 2021-03-29 16:02 ` [Bug gdb/27627] " tromey at sourceware dot org 2021-04-05 5:36 ` dinc.tarkan at gmail dot com 2021-04-05 5:43 ` dinc.tarkan at gmail dot com 2021-04-05 14:42 ` simark at simark dot ca 2021-04-06 6:13 ` dinc.tarkan at gmail 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-27627-4717@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).