From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22454-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 6599 invoked by alias); 2 Sep 2005 06:52:07 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 6567 invoked by uid 22791); 2 Sep 2005 06:51:58 -0000
Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 02 Sep 2005 06:51:58 +0000
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1EB5Nc-0002hK-0r
	for gdb@sources.redhat.com; Fri, 02 Sep 2005 08:50:28 +0200
Received: from zigzag.lvk.cs.msu.su ([158.250.17.23])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gdb@sources.redhat.com>; Fri, 02 Sep 2005 08:50:28 +0200
Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gdb@sources.redhat.com>; Fri, 02 Sep 2005 08:50:28 +0200
To: gdb@sources.redhat.com
From:  Vladimir Prus <ghost@cs.msu.su>
Subject:  Re: Auto variables display
Date: Fri, 02 Sep 2005 06:52:00 -0000
Message-ID:  <df8sn1$ivb$1@sea.gmane.org>
References:  <Pine.LNX.4.44.0509012055240.3590-100000@ispserv.ispras.ru>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7Bit
User-Agent: KNode/0.8.2
X-SW-Source: 2005-09/txt/msg00009.txt.bz2

Hi Konstantin,

> Hello, All.
> 
> In MS Visual Studio debugger there is a very convenient feature - "Auto"
> watch window tab, which displays the variables, referenced at the current
> program statement. I.e. when you step across "i=j;" it displays i and j,
> when you step across "x=f(a+b,*c)" displays a,b and c, etc.
> This allows to see automatically just the values that affect current step
> execution and see the error when and where it happens.
> 
> The question is: does GDB support something like this and also are
> there the debug info formats that provide the mapping of the source lines
> (or code addresses) to the set of variables, references at the point?

I suspect that MS debugger does not have such information either, and merely
looks at all identifiers at the current line and tries to fetch them. That
should be possible to implement using gdb, as well.

- Volodya