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 testsuite/28561] New: [gdb/testsuite] Error due to not reading \n at end of mi prompt Date: Mon, 08 Nov 2021 12:54:00 +0000 [thread overview] Message-ID: <bug-28561-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28561 Bug ID: 28561 Summary: [gdb/testsuite] Error due to not reading \n at end of mi prompt Product: gdb Version: 11.1 Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- In OBS, on openSUSE Tumbleweed for armv7hl, I run into: ... (gdb) ^M show mi-async^M &"show mi-async\n"^M ~"Whether MI is in asynchronous mode is off.\n"^M ^done^M (gdb) ^M 104-environment-directory -r^M 104^done,source-path="$cdir:$cwd"^M (gdb) ERROR: Dir reinitialization failed (timeout) ... I see similar fails for openSUSE Tumbleweed aarch64: ... 103-break-list^M 103^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="7",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}^M (gdb) ERROR: -break-list (timeout) ^M ... AFAIU, gdb produces the required output, but the test-suite emits an error just before the end of the mi prompt, just before '\r\n'. This could be a system or system load problem of some sort. I do find it curious though that the timeout always happens at the exact same location, so I thought it worthy of filing. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-11-08 12:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-08 12:54 vries at gcc dot gnu.org [this message] 2021-11-08 12:56 ` [Bug testsuite/28561] [gdb/testsuite] Error due to not reading \r\n " vries at gcc dot gnu.org 2021-11-08 13:05 ` vries at gcc dot gnu.org 2021-11-08 13:09 ` vries at gcc dot gnu.org 2022-05-09 7:18 ` luis.machado at arm dot com 2022-05-09 8:36 ` vries at gcc dot gnu.org 2022-05-09 10:15 ` luis.machado at arm dot com 2022-05-16 9:14 ` mark at klomp dot org 2022-05-16 9:25 ` mark at klomp dot org 2022-05-30 16:18 ` thiago.bauermann at linaro dot org 2022-05-31 8:40 ` mark at klomp dot org 2022-05-31 8:42 ` mark at klomp dot org 2022-05-31 9:07 ` vries at gcc dot gnu.org 2022-05-31 9:52 ` luis.machado at arm 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-28561-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).