From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 38E873854805; Tue, 23 Mar 2021 08:05:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 38E873854805 From: "dinc.tarkan at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dinc.tarkan at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2021 08:05:26 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27627 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 n= ame 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...". gdb understands the multiple packet format and con= tinues 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...." 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 d= ue to an error. I changed the connection type to TCP, nothing else changed and it works as expected. --=20 You are receiving this mail because: You are on the CC list for the bug.=