From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-34398-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 8056 invoked by alias); 15 May 2009 14:42:20 -0000
Received: (qmail 7932 invoked by uid 22791); 15 May 2009 14:42:10 -0000
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 May 2009 14:42:02 +0000
Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KJO00800WRVFD00@i-mtaout7.012.net.il> for gdb@sourceware.org; Fri, 15 May 2009 17:41:57 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.73.80]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KJO0002HWTWMQ20@i-mtaout7.012.net.il>; Fri, 15 May 2009 17:41:56 +0300 (IDT)
Date: Fri, 15 May 2009 14:42:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: overloading 'print' command.
In-reply-to: <8ac60eac0905150707n38e82ebcw49a4f46d476ef7f@mail.gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: pluto@agmk.net, gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83k54iqvgk.fsf@gnu.org>
References: <QXEMlZRc.1242301597.2053650.pluto@agmk.net> <8ac60eac0905141617g1db278e5l906eef8f5b899ed4@mail.gmail.com> <83preargj6.fsf@gnu.org> <8ac60eac0905150707n38e82ebcw49a4f46d476ef7f@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-05/txt/msg00084.txt.bz2

> Date: Fri, 15 May 2009 07:07:16 -0700
> From: Paul Pluzhnikov <ppluzhnikov@google.com>
> Cc: pluto@agmk.net, gdb@sourceware.org
> 
> I don't see how hook-print can help OP to do something special for
> std::string. The manual says hook-print doesn't get any arguments, so
> it can't even tell what is being printed. What am I missing?

Looks like I was missing something: the fact that hooks don't have
access to the arguments of the hooked command.  Sounds like a bad
limitation to me.