This is the mail archive of the gdb@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: clearing call stack when a new binary file is loaded

From: "Jiju George T" <jiju dot george at nestgroup dot net>
To: "'Daniel Jacobowitz'" <drow at false dot org>
Cc: <gdb at sources dot redhat dot com>
Date: Thu, 24 Apr 2008 17:24:53 +0100
Subject: RE: clearing call stack when a new binary file is loaded
References: <005101c8a52a$13f76910$390aa8c0@ashmicro.ashling.com> <fun4bj$voj$2@ger.gmane.org> <20080423114537.GA15843@caradoc.them.org> <00a601c8a541$1194f090$390aa8c0@ashmicro.ashling.com> <20080423125717.GA20157@caradoc.them.org>

Will it be fixed in the next release? Do I have to file a bug on this? 

-----Original Message-----
From: 'Daniel Jacobowitz' [mailto:drow@false.org] 
Sent: 23 April 2008 13:57
To: Jiju George T
Cc: 'Vladimir Prus'; gdb@sources.redhat.com
Subject: Re: clearing call stack when a new binary file is loaded

On Wed, Apr 23, 2008 at 01:53:46PM +0100, Jiju George T wrote:
> Is there any equivalent mi command to invalidate the frame cache? 

No.  If you use GDB 6.8 the CLI command "flushregs" will hack around
the problem but we simply need to fix it.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- clearing call stack when a new binary file is loaded
  - From: Jiju George T
- Re: clearing call stack when a new binary file is loaded
  - From: Vladimir Prus
- Re: clearing call stack when a new binary file is loaded
  - From: Daniel Jacobowitz
- RE: clearing call stack when a new binary file is loaded
  - From: Jiju George T
- Re: clearing call stack when a new binary file is loaded
  - From: 'Daniel Jacobowitz'

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