public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/28711] gdb closes when displaying structs with long field names in eclipse Date: Sat, 18 Dec 2021 11:39:08 +0000 [thread overview] Message-ID: <bug-28711-4717-nWU2NE11ma@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28711-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28711 --- Comment #3 from Andrew Burgess <aburgess at redhat dot com> --- I tried starting GDB without placing the MI interface onto a separate terminal, like this: ./gdb/gdb --data-directory ./gdb/data-directory/ --interpreter mi2 --nx -q -ex "set pagination off" -ex "show version" -ex "start" ./test.x Then pasted the same set of MI commands as before, and the test completes successfully. So it seems to be something about the way the separate MI interface is handled. I looked in top.c at `new_ui_command` function, and saw this comment: /* Open specified terminal. Note: we used to open it three times, once for each of stdin/stdout/stderr, but that does not work with Windows named pipes. */ So, on a whim I tried this patch: ### START ### diff --git a/gdb/top.c b/gdb/top.c index 1f9e649a85d..470881b5db6 100644 --- a/gdb/top.c +++ b/gdb/top.c @@ -366,10 +366,12 @@ new_ui_command (const char *args, int from_tty) /* Open specified terminal. Note: we used to open it three times, once for each of stdin/stdout/stderr, but that does not work with Windows named pipes. */ - gdb_file_up stream = open_terminal_stream (tty_name); + gdb_file_up stream1 = open_terminal_stream (tty_name); + gdb_file_up stream2 = open_terminal_stream (tty_name); + gdb_file_up stream3 = open_terminal_stream (tty_name); std::unique_ptr<ui> ui - (new struct ui (stream.get (), stream.get (), stream.get ())); + (new struct ui (stream1.get (), stream2.get (), stream3.get ())); ui->async = 1; @@ -380,7 +382,9 @@ new_ui_command (const char *args, int from_tty) interp_pre_command_loop (top_level_interpreter ()); /* Make sure the file is not closed. */ - stream.release (); + stream1.release (); + stream2.release (); + stream3.release (); ui.release (); } ### END ### And retested the original GDB command line (with separate MI interface), and now the problem is resolved. I don't know exactly means, but maybe someone else understands, I'll just keep digging... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-18 11:39 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-17 13:07 [Bug mi/28711] New: " cristian.lupascu at nxp dot com 2021-12-17 16:53 ` [Bug mi/28711] " aburgess at redhat dot com 2021-12-17 16:55 ` aburgess at redhat dot com 2021-12-18 11:39 ` aburgess at redhat dot com [this message] 2021-12-20 18:44 ` aburgess at redhat dot com 2021-12-24 17:03 ` fweimer at redhat dot com 2021-12-26 19:06 ` tromey at sourceware dot org 2021-12-27 10:15 ` Andrew Burgess 2021-12-27 10:15 ` aburgess at redhat dot com 2022-01-17 16:43 ` aburgess at redhat dot com 2022-02-07 10:25 ` cvs-commit at gcc dot gnu.org 2022-02-08 10:16 ` aburgess at redhat dot com 2022-02-09 19:48 ` cristian.lupascu at nxp dot com 2022-02-09 23:42 ` tromey at sourceware dot org 2022-10-31 16:48 ` jonah at kichwacoders dot com 2022-10-31 16:54 ` jonah at kichwacoders 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-28711-4717-nWU2NE11ma@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).