public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1: target remote (got interactive prompt) Date: Sat, 21 Mar 2020 14:22:32 +0000 [thread overview] Message-ID: <bug-25475-4717-n5pfj7Zi55@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25475 --- Comment #16 from philippe.waroquiers at skynet dot be --- I evaluated the change to ask the question independently of the fact that the current loaded file has symbols, i.e. removing the following part of the condition : (have_full_symbols () || have_partial_symbols ()) to ask the "Load new symbol table" question. This seems to be a significant change in behaviour that triggers about 1200 new failures in the gdb testsuite. The ratio (cost+risk)/benefit looks poor for this change. Another possible way to fix this is to replace the value "ask" by "load" (and explain in the doc that typically, a question is asked before loading the new file): (gdb) h set exec-file-mismatch Set exec-file-mismatch handling (load|warn|off). Specifies how to handle a mismatch between the current exec-file name loaded by GDB and the exec-file name automatically determined when attaching to a process: load - warn the user and load the determined exec-file. warn - warn the user, but do not change the exec-file. off - do not check for mismatch. (gdb) WDYT ? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-21 14:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25475-4717@http.sourceware.org/bugzilla/> 2020-03-15 14:18 ` vries at gcc dot gnu.org 2020-03-21 14:22 ` philippe.waroquiers at skynet dot be [this message] 2020-03-21 17:49 ` vries at gcc dot gnu.org 2020-06-16 0:08 ` brobecker at gnat dot com 2020-06-17 14:46 ` vries at gcc dot gnu.org 2020-06-21 11:21 ` philippe.waroquiers at skynet dot be 2020-06-21 17:26 ` brobecker at gnat dot com 2020-06-21 17:33 ` philippe.waroquiers at skynet dot be 2020-06-21 19:46 ` philippe.waroquiers at skynet dot be 2020-06-24 20:44 ` cvs-commit at gcc dot gnu.org 2020-06-26 20:02 ` philippe.waroquiers at skynet dot be 2020-06-26 20:07 ` brobecker at gnat 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-25475-4717-n5pfj7Zi55@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).