From: Marc Mason <mpeg.blue@free.fr>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: x commands in history
Date: Thu, 16 Apr 2009 11:15:00 -0000 [thread overview]
Message-ID: <49E6F3BB.5070801@free.fr> (raw)
In-Reply-To: <20090415171633.GA19061@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Wed, Apr 15, 2009 at 06:11:34PM +0200, Marc Mason wrote:
>> Daniel Jacobowitz wrote:
>>> On Wed, Apr 15, 2009 at 04:19:45PM +0200, Marc Mason wrote:
>>>
>>>> However, on this embedded platform, when I scroll through the commands
>>>> history, the "addr" part of the x command is always discarded...
>>>
>>> What platform? What version of GDB?
>>
>> I was under the impression that my issue was a feature, not a bug, which
>> is why I didn't think the details you ask for would be important.
>>
>> GNU gdb 6.5-ST-1.0-ST40 [build Feb 23 2007]
>> I connect to the embedded board via an ST micro connect device.
>
> If it's a feature, it's one ST's added - but I think it's a bug that
> was fixed, related to how the x command repeats when you press enter.
Strange...
I've been using gdb for years, and I've never had that problem before.
Something in the setup must be different.
I'll look into ST-specific options.
> That's a pretty old baseline GDB version.
We are, indeed, using an ancient tool chain (released in 2007).
# binutils 2.16.91.0.5
# GCC 4.1.1
# GDB 6.5
# newlib 1.14.0
while the latest tool chain provides
# binutils 2.18.50.0.4
# GCC 4.2.4
# GDB 6.8
# gmake 3.80
# newlib 1.16.0
--
Regards.
next prev parent reply other threads:[~2009-04-16 9:00 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 [this message]
2009-04-16 17:06 ` Antony KING
2009-04-17 13:12 ` Marc Mason
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=49E6F3BB.5070801@free.fr \
--to=mpeg.blue@free.fr \
--cc=drow@false.org \
--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