This is the mail archive of the gdb-patches@sources.redhat.com 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] |
Hello,
Try running up insight and then, in the console window, typing:
maint internal-error my message
A totally meaningless pop-up containing:
Do you want to quit gdb?
appears. Now imagine this poping up when you weren't expecting it. Helpful? Not.
The attached modifies the internal-error code so that the entire problem string is passed into query(). By doing this insight, and MI have the full problem text, and not just the meaningless final line.
It does mean that, for the CLI, the problem text appears twice. Given how distasterious an internal error is, I don't think that is a problem.
2003-06-22 Andrew Cagney <cagney@redhat.com>
* utils.c (internal_vproblem): Print the problem to a reason buffer and then pass to query. Make the msg variable more local.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |