From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3723 invoked by alias); 27 Jun 2005 22:03:47 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3712 invoked by uid 22791); 27 Jun 2005 22:03:41 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 27 Jun 2005 22:03:41 +0000 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1Dn1hb-0000OZ-K4; Mon, 27 Jun 2005 18:03:39 -0400 Date: Mon, 27 Jun 2005 22:03:00 -0000 From: Daniel Jacobowitz To: Thomas Glanzmann , gdb@sources.redhat.com Subject: Re: Tracing all 'call' instructions in a gdb session Message-ID: <20050627220339.GA1457@nevyn.them.org> Mail-Followup-To: Thomas Glanzmann , gdb@sources.redhat.com References: <20050627220122.GF8659@cip.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050627220122.GF8659@cip.informatik.uni-erlangen.de> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00271.txt.bz2 On Tue, Jun 28, 2005 at 12:01:22AM +0200, Thomas Glanzmann wrote: > Hello, > I like to trace every 'call instruction' in a executable. How do I > obtain this with gdb or are there other tools to obtain that? > > Like tracepoint every call instruction and gather eip and 'jump to' > address? 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. A profiler might be a better tool. I bet you can get valgrind to do this somehow. -- Daniel Jacobowitz CodeSourcery, LLC