From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7128 invoked by alias); 10 Jul 2006 20:43:38 -0000 Received: (qmail 7110 invoked by uid 22791); 10 Jul 2006 20:43:37 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 10 Jul 2006 20:43:34 +0000 Received: from relay7.apple.com (a17-128-113-37.apple.com [17.128.113.37]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id k6AKgvkt019054; Mon, 10 Jul 2006 13:42:57 -0700 (PDT) Received: from [17.201.22.240] (unknown [17.201.22.240]) by relay7.apple.com (Apple SCV relay) with ESMTP id 8D334149; Mon, 10 Jul 2006 13:42:57 -0700 (PDT) Date: Mon, 10 Jul 2006 20:43:00 -0000 Content-Transfer-Encoding: 7bit Cc: Nick Roberts , gdb@sourceware.org From: Jim Ingham In-Reply-To: <20060621023258.GA19167@nevyn.them.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Subject: Re: MI: event notification References: <17560.40409.61785.698765@kahikatea.snap.net.nz> <20060621013437.GA17956@nevyn.them.org> <17560.44395.508930.351917@kahikatea.snap.net.nz> <20060621023258.GA19167@nevyn.them.org> To: Daniel Jacobowitz Mime-Version: 1.0 (Apple Message framework v816) Message-Id: <0DEBAC0A-BF26-414A-ABE6-DFE5105A684C@apple.com> X-Mailer: Apple Mail (2.816) 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-07/txt/msg00022.txt.bz2 We don't do what Nick's suggesting. We do do something similar for shared library notifications - we emit async notifications for shared library load events from gdb so Xcode doesn't have to stop on solib events & get the shlig list. Similarly if a shared library load causes a pended breakpoint to get loaded we tell about that as well. But we don't do anything for stack changes. Note, except in the case where you have gotten stuck in some kind of pathological recursion, I would be surprised if it's consing up the stack list for the MI that takes a significant portion of the time, so I'm not sure this example isn't a false optimization. But anyway, we don't do that. Most of the notifications we use are to tell Xcode what's happening during -interpreter-exec, so it can keep the UI in sync with the console. The On Jun 20, 2006, at 7:32 PM, Daniel Jacobowitz wrote: >> 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. > > Yes, I know that Jim was planning to list off their MI changes for the > DMI workgroup, at some point. >