This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Backtrace prints wrong argument value

From: Daniel Jacobowitz <drow at false dot org>
To: Luis Machado <luisgpm at linux dot vnet dot ibm dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Wed, 16 May 2007 11:23:25 -0400
Subject: Re: [patch] Backtrace prints wrong argument value
References: <1177527233.12599.42.camel@localhost> <20070425191304.GA1283@caradoc.them.org> <1179293640.4323.16.camel@localhost> <20070516144250.GD24682@caradoc.them.org> <1179328781.4295.13.camel@localhost>

On Wed, May 16, 2007 at 12:19:41PM -0300, Luis Machado wrote:
> If there is a way to temporarily store those values that we know for
> sure that will be wasted during the next inner frame's function
> execution, we could recover them during backtrace. That could add some
> complexity to the unwinding procedure though.

This is, generally speaking, impossible.  I hadn't thought of the
init_frame_regs hook last time I looked at this; I hope it helps.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Re: [patch] Backtrace prints wrong argument value
  - From: Luis Machado
- Re: [patch] Backtrace prints wrong argument value
  - From: Daniel Jacobowitz
- Re: [patch] Backtrace prints wrong argument value
  - From: Luis Machado

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]