This is the mail archive of the
mailing list for the GDB project.
Re: [patch] PR python/11407
On Fri, Jun 25, 2010 at 11:25 AM, Tom Tromey <email@example.com> wrote:
>>>>>> "Phil" == Phil Muldoon <firstname.lastname@example.org> writes:
> Phil> I'm not sure what to do in this case. ?There seems to be no direct
> Phil> equivalent of converting an exception to error output on a stream in MI
> Phil> (or any cases of TRY ... exception handlers). ?There are many cases of
> Phil> MI raising an error() though, so I thought it appropriate in our case
> Phil> to raise a warning() instead. ?Because of the peculiarities of the MI
> Phil> cases I just report a warning generically and move on. ?This is not
> Phil> totally ideal, but it does allow the error/warning preamble followed
> Phil> by the actual locals information.
> I'm not convinced a warning is the best thing.
> Why not catch the exception and print the text of it as the variable's
> value? ?Something like ?<error reading variable: %s>
> I think this will work ok with existing front ends.
I like this, fwiw.