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>, "'Vladimir Prus'" <vladimir at codesourcery dot com>
Cc: <gdb at sources dot redhat dot com>
Date: Wed, 23 Apr 2008 13:53:46 +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>

Is there any equivalent mi command to invalidate the frame cache? 

Thanks,
Jiju

-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf
Of Daniel Jacobowitz
Sent: 23 April 2008 12:46
To: Vladimir Prus
Cc: gdb@sources.redhat.com
Subject: Re: clearing call stack when a new binary file is loaded

On Wed, Apr 23, 2008 at 02:51:35PM +0400, Vladimir Prus wrote:
> Which version of GDB?

I expect it still does this.  write_pc doesn't invalidate the frame
cache, so we should manually do so at the end of generic_load.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: clearing call stack when a new binary file is loaded
  - From: 'Daniel Jacobowitz'

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

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