From: "taylor, david" <David.Taylor@dell.com>
To: "paul@mad-scientist.net" <paul@mad-scientist.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: gdbserver with a core file?
Date: Thu, 01 Mar 2018 13:54:00 -0000 [thread overview]
Message-ID: <63F1AEE13FAE864586D589C671A6E18B10FB5B11@MX203CL03.corp.emc.com> (raw)
In-Reply-To: <1519909479.3684.41.camel@mad-scientist.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 915 bytes --]
I don't know if anyone has added such functionality to gdbserver; but, with regards to
the problem you're trying to solve -- I've faced similar ones in the past.
If you use emacs, you might consider gud plus a small shell script or two.
I've used in in the past to solve the problem where I have GDB and the executable
remote but sources local.
In emacs, do
M-x gdb
when prompted for how to run gdb, replace gdb with the path to a shell script that
. sets up the local environment (if needed)
. invokes ssh -- something like:
ssh remote-host /path/to/remote/shell/script
where the remote shell script does a cd if needed, creates a gdb init file if appropriate
and / or needed, and then invokes gdb with appropriate arguments.
GDB communicates with Emacs. When you stop / step / next / whatever,
GDB tells Emacs what it needs to know. Sources stay local.
\x16º&ÖëzÛ«·ãÉb²Ö«r\x18\x1d
prev parent reply other threads:[~2018-03-01 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 13:04 Paul Smith
2018-03-01 13:54 ` taylor, david [this message]
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=63F1AEE13FAE864586D589C671A6E18B10FB5B11@MX203CL03.corp.emc.com \
--to=david.taylor@dell.com \
--cc=gdb@sourceware.org \
--cc=paul@mad-scientist.net \
/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: link
Be 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