From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21989-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 11367 invoked by alias); 27 Jun 2005 22:10:16 -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 11343 invoked by uid 22791); 27 Jun 2005 22:10:12 -0000
Received: from faui03.informatik.uni-erlangen.de (HELO faui03.informatik.uni-erlangen.de) (131.188.30.103)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 27 Jun 2005 22:10:12 +0000
Received: from faui03.informatik.uni-erlangen.de (faui03.informatik.uni-erlangen.de [131.188.30.103])
	by faui03.informatik.uni-erlangen.de (8.12.9/8.12.9) with ESMTP id j5RMAAS8023817
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <gdb@sources.redhat.com>; Mon, 27 Jun 2005 22:10:10 GMT
Received: (from sithglan@localhost)
	by faui03.informatik.uni-erlangen.de (8.12.9/8.12.9) id j5RMAABf023816
	for gdb@sources.redhat.com; Tue, 28 Jun 2005 00:10:10 +0200 (CEST)
Date: Mon, 27 Jun 2005 22:10:00 -0000
From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: gdb@sources.redhat.com
Subject: Re: Tracing all 'call' instructions in a gdb session
Message-ID: <20050627221010.GG8659@cip.informatik.uni-erlangen.de>
Mail-Followup-To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
	gdb@sources.redhat.com
References: <20050627220122.GF8659@cip.informatik.uni-erlangen.de> <20050627220339.GA1457@nevyn.them.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050627220339.GA1457@nevyn.them.org>
User-Agent: Mutt/1.5.9i
X-SW-Source: 2005-06/txt/msg00272.txt.bz2

Hello,

> Sorry, GDB can't help you with this.  Not today, anyway.  You'd need
> both tracepoints and a more flexible facility for setting breakpoints
> automatically.

What about using objdump and grep setting a few hunderd tracepoints?
Would that work?

> A profiler might be a better tool.  I bet you can get valgrind to do
> this somehow.

I thought exactly the same. I am going to ask this on the valgrind ml.
;-) But it shouldn't be a problem if valgrind simulates the call
instruction.

	Thomas