From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8017 invoked by alias); 18 Apr 2006 16:40:17 -0000 Received: (qmail 8009 invoked by uid 22791); 18 Apr 2006 16:40:16 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out3.apple.com (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Apr 2006 16:40:13 +0000 Received: from relay5.apple.com (a17-128-113-35.apple.com [17.128.113.35]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id k3IGdu85015271; Tue, 18 Apr 2006 09:39:56 -0700 (PDT) Received: from [17.201.22.240] (unknown [17.201.22.240]) by relay5.apple.com (Apple SCV relay) with ESMTP id D462D324014; Tue, 18 Apr 2006 09:39:54 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1CE7391B-7261-49BD-9068-89C201F555DE@apple.com> Cc: gdb@sources.redhat.com Content-Transfer-Encoding: 7bit From: Jim Ingham Subject: Re: MI: performance of getting stack arguments Date: Tue, 18 Apr 2006 19:11:00 -0000 To: Vladimir Prus X-Mailer: Apple Mail (2.749.3) 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-04/txt/msg00250.txt.bz2 Do you really have a UI that shows the stack arguments for ALL the frames on the stack? That's very unusual (and visually a bit overwhelming, I would imagine). The usual stack display shows the stack with just the function names. Then clicking on any given stack will populate the arguments for that frame, fill the source window with the source for that frame, etc... This way, you only need to fetch the arguments for the bottom-most frame on the stack when you stop stepping. You would only fetch the other stack arguments if the user specifically requests them. For most purposes, when you are stepping through a function you don't really care what the arguments higher up on the stack are, and even if you want to see them once you rarely need to see if they are changing after each step. Having them always visible sounds like it would make the UI very noisy. Fetching them without displaying them is a waste of time, since you can fetch them one by one on demand. Jim On Apr 18, 2006, at 9:10 AM, Vladimir Prus wrote: > > Hi, > I've run into a performance problem with "-stack-list-arguments 1" > command. > I issue the command in order to obtain stack arguments for all > frames, and > I've 129 frames. Each frame has just a couple of arguments. > However, the > command execution takes 608 ms. > > If this command is issued repeatedly, the time is roughly the same. > > 1. Any ideas why the command takes so long? > > 2. Any ideas what should I do to to avoid making user wait half-a- > second on > each "step"? I can try to reload stack only when current frame id > changes. > But then, each time I enter a new function, there's still that > half-a-second delay. > > Incidentally, it seems that Eclipse does no show arguments in stack > view at > all, but that does not seem the right solution. > > - Volodya > >