public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/27541] gdb crashes on "file -readnow" Date: Mon, 08 Mar 2021 17:19:36 +0000 [thread overview] Message-ID: <bug-27541-4717-375GXpIgAp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27541-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27541 --- Comment #3 from Simon Marchi <simark at simark dot ca> --- I tried with both master and gdb-10-branch, and I don't see a problem: $ ./gdb -nx --data-directory=data-directory ~/Downloads/a -readnow ... Reading symbols from /home/simark/Downloads/a... Expanding full symbols from /home/simark/Downloads/a... (gdb) What version of GDB are you testing with? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-08 17:19 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-08 2:16 [Bug symtab/27541] New: " liangjs at pku dot edu.cn 2021-03-08 2:45 ` [Bug symtab/27541] " simark at simark dot ca 2021-03-08 5:25 ` liangjs at pku dot edu.cn 2021-03-08 17:19 ` simark at simark dot ca [this message] 2021-03-09 3:06 ` liangjs at pku dot edu.cn 2021-03-09 4:17 ` simon.marchi at polymtl dot ca 2021-03-09 4:26 ` simon.marchi at polymtl dot ca 2021-03-09 5:05 ` simon.marchi at polymtl dot ca 2021-03-10 2:47 ` brobecker at gnat dot com 2021-03-11 3:19 ` simon.marchi at polymtl dot ca 2021-03-15 17:16 ` simark at simark dot ca 2021-03-30 17:37 ` cvs-commit at gcc dot gnu.org 2021-03-30 17:38 ` cvs-commit at gcc dot gnu.org 2021-03-30 17:39 ` simark at simark dot ca 2021-06-27 18:01 ` ahmedsayeed1982 at yahoo dot com 2021-09-02 11:06 ` donipah907 at mtlcz dot com 2021-09-02 11:13 ` mark at klomp dot org 2021-09-05 7:34 ` kimolsun2020 at yahoo dot com 2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk 2021-09-06 9:13 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:38 ` mehmetgelisin at aol dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-09 17:44 ` svitvitraga at gmail dot com 2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:13 ` progonsaytu at gmail dot com 2021-10-24 10:01 ` glassmtech at ukr dot net 2021-11-13 19:34 ` tesaso8237 at funboxcn dot com 2021-11-19 6:37 ` aslanelli50 at gmail dot com 2021-11-22 6:48 ` gexed96894 at keagenan dot com 2021-11-24 13:41 ` allen at rockvalleymarketing 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-27541-4717-375GXpIgAp@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).