From: Marc Mason <mpeg.blue@free.fr>
To: Antony KING <antony.king@st.com>
Cc: gdb@sourceware.org
Subject: Re: x commands in history
Date: Fri, 17 Apr 2009 13:12:00 -0000 [thread overview]
Message-ID: <49E836C9.5050308@free.fr> (raw)
In-Reply-To: <49E72F63.1050201@st.com>
Antony KING wrote:
> By any chance when you experience this problem is it when you use the
> command console of Insight GUI interface ?
Yes, I am using the GUI.
gdb is started with the following command.
sh4gdb -q -w -x foo.cmd -ex foo.bin
> If so then this is a known issue.
How do I tell which version of Insight I'm running?
Has this bug been fixed in newer releases?
NB: the "About GDB" item in the "Help" menu of the "Source Window"
mentions "GNUPro Toolkit Insight Debugger"
> Try using the TUI interface instead.
I suppose I could do that, but it would be less convenient.
I might have to learn to live with the bug.
Thanks for the heads up.
--
Regards.
next prev parent reply other threads:[~2009-04-17 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 14:21 Marc Mason
2009-04-15 16:00 ` Daniel Jacobowitz
2009-04-15 17:16 ` Marc Mason
2009-04-15 17:34 ` Daniel Jacobowitz
2009-04-16 11:15 ` Marc Mason
2009-04-16 17:06 ` Antony KING
2009-04-17 13:12 ` Marc Mason [this message]
2009-04-17 19:48 ` Antony KING
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=49E836C9.5050308@free.fr \
--to=mpeg.blue@free.fr \
--cc=antony.king@st.com \
--cc=gdb@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: 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