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] Fix ptype problem printing typedefs defined differently in different compilation units

From: Fred Fish <fnf at specifix dot com>
To: Jim Blandy <jimb at red-bean dot com>
Cc: gdb-patches at sourceware dot org, fnf at specifix dot com
Date: Wed, 4 Jan 2006 06:15:14 -0500
Subject: Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
References: <200601031517.50309.fnf@specifix.com> <200601032147.14083.fnf@specifix.com> <8f2776cb0601031945gb876b84i48c145c291ecbcee@mail.gmail.com>
Reply-to: fnf at specifix dot com

On Tuesday 03 January 2006 22:45, Jim Blandy wrote:

> What would break if get_selected_block used, in the absence of a
> frame, the current source position?  Or, if get_selected_block really
> needs to return zero when there's no stack, what would break if
> parse_exp_in_context used the current source position as a fallback
> when get_selected_block returns zero?  It seems reasonable to me.

Excellent questions.  Sounds like reasonable things to investigate for
alternative solutions.  I'll give it a try and see...

-Fred

References:
- [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
  - From: Fred Fish
- Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
  - From: Fred Fish
- Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
  - From: Jim Blandy

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