verbose terminate_handler

[Gabriel Dos Reis]

Jason Merrill <jason@redhat.com> writes:

| [1  <text/plain>]
| I just whipped this up for a customer who requested that a call to
| terminate() print some information about the exception which caused it, as
| apparently the SunPro C++ does.  It prints the demangled name of the
| exception type and, for objects derived from exception, the result of
| what().

Cool!

[...]

| My question is, how much of this should go into the distribution?  I see
| several (largely orthogonal) options:
| 
| 1) Nothing.  Let anyone who wants this functionality reinvent it
|    themselves.  This is complicated by its reliance on ABI internals.

I don't favor this.

| 2) Add current_exception_type to libsupc++, perhaps to the ABI
|    specification.  This would avoid the need to look at the unwinder
|    headers.

Yes.

Thanks,

-- Gaby