Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units

[Jim Blandy <jimb at red-bean dot com>]

Are you sure you're not misunderstanding your typescript?  When you
have a core file, you have a frame, so it's always using the frame
context.  I think that's the correct behavior.  When there is a frame,
the source position (as established by 'list' commands) generally
doesn't override the frame position when deciding scopes.  It's the
same for (say) printing static variables.

What behavior would be most easily understood and used is arguable,
but this is, as I understand it, GDB's intended behavior.

So I don't think there's a problem with your patch.