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: Understanding GDB frames

From: Daniel Jacobowitz <drow at false dot org>
To: Maxim Grigoriev <maxim at tensilica dot com>
Cc: Jim Blandy <jimb at codesourcery dot com>, gdb at sourceware dot org, Marc Gauthier <marc at tensilica dot com>, Ross Morley <ross at tensilica dot com>
Date: Tue, 22 May 2007 22:24:33 -0400
Subject: Re: Understanding GDB frames
References: <46521C04.7040405@hq.tensilica.com> <m3y7jgbt7j.fsf@codesourcery.com> <465341B8.9060208@hq.tensilica.com> <m34pm476qn.fsf@codesourcery.com> <4653924D.5030304@hq.tensilica.com>

On Tue, May 22, 2007 at 06:01:01PM -0700, Maxim Grigoriev wrote:
> Anyway, doesn't it look like a reasonably inexpensive improvement ?

Why should we improve it this way?

I haven't seen any compelling reason.  Jim's already said that you
can't rely on frame ID equality in all cases - this stuff is
tricky to reason about, which is exactly why we try not to export the
frame IDs to the MI client.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: Understanding GDB frames
  - From: Maxim Grigoriev

References:
- Understanding GDB frames
  - From: Maxim Grigoriev
- Re: Understanding GDB frames
  - From: Jim Blandy
- Re: Understanding GDB frames
  - From: Maxim Grigoriev
- Re: Understanding GDB frames
  - From: Jim Blandy
- Re: Understanding GDB frames
  - From: Maxim Grigoriev

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