public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/14479] New: no way to request gdb to load separate debuginfo Date: Thu, 16 Aug 2012 15:58:00 -0000 [thread overview] Message-ID: <bug-14479-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14479 Bug #: 14479 Summary: no way to request gdb to load separate debuginfo Product: gdb Version: unknown Status: NEW Severity: enhancement Priority: P2 Component: symtab AssignedTo: unassigned@sourceware.org ReportedBy: tromey@redhat.com Classification: Unclassified I was debugging a program. gdb suggested I install some separate debuginfo packages (I think this is a Fedora extension -- but it doesn't matter since the problem here is generic). I wanted one of these, so in a separate window I ran debuginfo-install. At this point I wanted to tell gdb to try again to load the separate debuginfo. However, there's no convenient way to do this. "sharedlibrary" doesn't work. "add-symbol-file" might work but it is a pain. I think the simplest would be to make "sharedlibrary" do it. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-08-16 15:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-16 15:58 tromey at redhat dot com [this message] 2012-08-22 15:08 ` [Bug symtab/14479] " palves at redhat dot com 2012-08-22 16:05 ` tromey at redhat dot com 2013-06-07 16:54 ` tromey at redhat 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-14479-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).