From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2679 invoked by alias); 21 Jun 2006 02:23:42 -0000 Received: (qmail 2668 invoked by uid 22791); 21 Jun 2006 02:23:40 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Jun 2006 02:23:36 +0000 Received: from kahikatea.snap.net.nz (p458-tnt1.snap.net.nz [202.124.111.204]) by viper.snap.net.nz (Postfix) with ESMTP id 60BF276C32F; Wed, 21 Jun 2006 14:23:34 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id DFAE51D3550; Wed, 21 Jun 2006 14:22:39 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17560.44395.508930.351917@kahikatea.snap.net.nz> Date: Wed, 21 Jun 2006 02:31:00 -0000 To: Daniel Jacobowitz Cc: gdb@sourceware.org Subject: Re: MI: event notification In-Reply-To: <20060621013437.GA17956@nevyn.them.org> References: <17560.40409.61785.698765@kahikatea.snap.net.nz> <20060621013437.GA17956@nevyn.them.org> X-Mailer: VM 7.19 under Emacs 22.0.50.22 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00165.txt.bz2 > > Using the patch, "=stack-changed\n" gets printed every time the stack > > changes e.g > > Good idea in general, bad choice of example. This is not a valid > optimization, at least not where you put it. > > - Stepping within a frame can change the values displayed by > -stack-list-arguments. On most targets + compilers they > are sometimes corrupt at the beginning of a function. On > many targets the "incoming" value of the argument changes > when that variable is assigned to. In this case, though, -stack-list-frames would be unchanged? > - You can encounter the same frame ID for two consecutive stops > but have a different backtrace, e.g. if you continued and then > hit a breakpoint near the same function. Do you mean that with something like: ... myproc (arg1); myproc (arg2); the frame id on the second call to myproc would be identical to the first? Presumably the output to -stack-list-frames would be unchanged in this case also. > A good place to start might be asking the Xcode folks where they put > events. I know they put a bunch of them, e.g. shlib related. I don't > know if they're all suitable for GDB/MI, but I bet most of them are. > (And I think I talked with Jim about this particular one at some point, > and they either didn't have one, or didn't use it for much). If they can give me a few clues that will be great, but I only want to trawl through the code in Darwin, like I did for the asynchronous stuff, as a last resort. I am hoping that this will be an easier nut to crack. -- Nick http://www.inet.net.nz/~nickrob