public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/15651] New: set sysroot remote: is not enough Date: Wed, 19 Jun 2013 19:21:00 -0000 [thread overview] Message-ID: <bug-15651-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15651 Bug ID: 15651 Summary: set sysroot remote: is not enough Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Host: x86_64-unknown-linux-gnu Target: x86_64-unknown-linux-gnu One usually needs to type more commands than just "set sysroot remote:". (gdb) set sysroot remote: (gdb) target extended-remote hostname:port (gdb) set remote exec-file /path/to/program (gdb) file /path/to/program - local copy (gdb) start - GDB could download even exec_bfd from remote:. (gdb) set sysroot remote: (gdb) target remote hostname:port (gdb) symbol-file remote:/path/to/program (gdb) tbreak main (gdb) continue (gdb) sharedlibrary - why is symbol-file needed here when remote gdbserver already has the file? (Unrelated bug - "sharedlibrary" command should not be needed there.) These example come from my experiments in 2012: http://people.redhat.com/jkratoch/gdb2012.pdf -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-06-19 19:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-19 19:21 jan.kratochvil at redhat dot com [this message] 2014-02-21 15:51 ` [Bug remote/15651] set sysroot remote: is not enough for command symbol-file jan.kratochvil at redhat dot com 2014-02-21 15:57 ` jan.kratochvil at redhat dot com 2015-04-02 12:49 ` gbenson 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-15651-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).