From: Sorin Otescu <sorinu@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for hooking prefix commands
Date: Wed, 09 Mar 2011 15:08:00 -0000 [thread overview]
Message-ID: <4D7791D6.1040708@gmail.com> (raw)
In-Reply-To: <83fwqwpf0f.fsf@gnu.org>
On 03/09/2011 04:03 PM, Eli Zaretskii wrote:
>> Date: Wed, 09 Mar 2011 15:54:41 +0200
>> From: Sorin Otescu<sorinu@gmail.com>
>>
>>> Are you saying that 7.2 already supports this feature? Or are you
>>> saying that it's documented there, but doesn't work?
>>>
>> It's documented there, but I can't test it ATM, because I'm using a gdb
>> from a toolchain and it's not
>> easy for me to switch to 7.2. Maybe somebody can shed a light on the issue.
> I just tried this (with "info breakpoints") in GDB 7.2, and it worked
> for me.
>
> So I think you should upgrade when you can, and then you will have
> this feature.
>
Thanks ! That's what you get for using obsolete software and not RTFM :)
prev parent reply other threads:[~2011-03-09 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 12:35 Sorin Otescu
2011-03-09 12:58 ` Eli Zaretskii
2011-03-09 13:36 ` Sorin Otescu
2011-03-09 14:01 ` Eli Zaretskii
2011-03-09 14:03 ` Sorin Otescu
2011-03-09 14:15 ` Eli Zaretskii
2011-03-09 14:22 ` Eli Zaretskii
2011-03-09 15:08 ` Sorin Otescu [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=4D7791D6.1040708@gmail.com \
--to=sorinu@gmail.com \
--cc=gdb-patches@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