Re: [patch] Fix `return' of long/long-long results with no debuginfo

Joel Brobecker
2009-03-11T20:59:13Z

> The original patch was motivated by a case where casting to int gave a
> bad result. Then Mark had a counter-proposal, which was to use the
> expression's type, rather than assuming 'int'. Finally, I suggested
> simply requiring a cast, resulting in this patch.

Ah, OK - I didn't understand the final decision very well. Sorry about
that.

I'm starting to understand what the error message is trying to say, now.
Can we maybe explore other suggestions? I can suggest for instance:

Return value type not available for selected stack frame.\n
Please use an explicit cast of the value to return.

I think we should also probably add a note in the documentation as well.
In case a user still gets confused as to why he gets an error.

> So, the real question for you is how you think it ought to work.

Yes, I think so.

--
Joel