From: Tom Tromey <tromey@redhat.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs, gdb and runsparc.
Date: Mon, 24 Nov 2008 16:08:17 -0700 [thread overview]
Message-ID: <m3tz9wyb6m.fsf@fleche.redhat.com> (raw)
In-Reply-To: 755dc0f1-561c-4be7-912b-98e526ad878a@t3g2000yqa.googlegroups.com
>>>>> ">" == kidologie <richwellum@gmail.com> writes:
>> The simulator being used is runsol/runsparc. Outside of emacs, I would
>> do 'runsparc gdb ./<image>' and this works fine. But through emacs I
>> am having issues. For example:
>> I think what's going on essentially is that, gdb emacs is being handed
>> an additional command: runsol, which it is interpreting as being the
>> debugger. The additional file names are treated as files to be
>> debugged. By pre-pending the fully-qualified path, emacs is forcing
>> the change to the CWD to that path.
Yeah. I've been bit by this myself.
>> So I think I need an emacs hook to handle this integration? An
>> alternative is to actually copy 'gdb' to the working directory and
>> then this works: M-x gdb: runsparc ./gdb ./<image>
One workaround would be a shell script which invokes 'runsparc gdb $@'.
Tom
prev parent reply other threads:[~2008-11-24 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 21:22 Emacs, gdb and runsparc kidologie
2008-11-24 23:08 ` Tom Tromey [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3tz9wyb6m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=help-gnu-emacs@gnu.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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).