From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22655 invoked by alias); 26 Dec 2007 20:45:32 -0000 Received: (qmail 22647 invoked by uid 22791); 26 Dec 2007 20:45:31 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 26 Dec 2007 20:45:22 +0000 Received: from zps18.corp.google.com (zps18.corp.google.com [172.25.146.18]) by smtp-out.google.com with ESMTP id lBQKjHrH023302 for ; Wed, 26 Dec 2007 12:45:17 -0800 Received: from wa-out-1112.google.com (wahv27.prod.google.com [10.114.248.27]) by zps18.corp.google.com with ESMTP id lBQKjAoX000368 for ; Wed, 26 Dec 2007 12:45:16 -0800 Received: by wa-out-1112.google.com with SMTP id v27so3984465wah.4 for ; Wed, 26 Dec 2007 12:45:16 -0800 (PST) Received: by 10.114.93.17 with SMTP id q17mr6742148wab.70.1198701916708; Wed, 26 Dec 2007 12:45:16 -0800 (PST) Received: by 10.114.13.5 with HTTP; Wed, 26 Dec 2007 12:45:16 -0800 (PST) Message-ID: Date: Wed, 26 Dec 2007 20:45:00 -0000 From: "Doug Evans" To: "Paul Koning" Subject: Re: memory search capability Cc: "Michael Snyder" , gdb@sourceware.org In-Reply-To: <86A3089001A44141B76B882059E7E53B032DB53C@M31.equallogic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1198283677.18985.74.camel@localhost.localdomain> <86A3089001A44141B76B882059E7E53B032DB53C@M31.equallogic.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00179.txt.bz2 I'm guessing there's general agreement in getting this functionality into gdb. Can you post the patch? I have some time to help work on it. Regarding examining the results of the search: I'm guessing the way to handle that is in Python (once it's added). On 12/26/07, Paul Koning wrote: > I've implemented this as a local mod. Right now it doesn't have support > in the remote protocol, that's on the "to do next" list. > > One bit of user feedback I got was to drop the results of the search > into some local variables so scripts could use that. > > Any suggestions for a suitable encoding for this in the packet protocol? > > I could submit the code to the list if there's interest. > > paul > > > -----Original Message----- > > From: gdb-owner@sourceware.org > > [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder > > Sent: Friday, December 21, 2007 7:35 PM > > To: Doug Evans > > Cc: gdb@sourceware.org > > Subject: Re: memory search capability > > > > > > On Fri, 2007-12-21 at 16:21 -0800, Doug Evans wrote: > > > Anyone know of any work in this area since this? > > > > > > http://www.cygwin.com/ml/gdb/2001-03/msg00071.html > > > > I don't think so. Every now and then, someone remarks that it > > would seem like a good idea. No one ever does it. Shouldn't be > > that hard... > > > > > > > > >