set_unexpected with arguments

[noobcpp]

The signature of set_unexpected handler doesn't take any argument.

But I want to print which Exception hass been occured along with the error message from the set_unexpected callback function !!

So How can it be made possible.
I dont want to patch GCC's files.

It Can also be done If set_unexpected(std::exception) overload exists.
or there exists some way to get the last raised uncaught exception somehow.
or may be some other way too..

[noobcpp]

I've got an Idea
Put main in a try catch block that catches all kinda exception either by ... or by std::exception

[Neo1]

I've got an Idea
Put main in a try catch block that catches all kinda exception either by ... or by std::exception

All executable code must be _within_ main, including try/catch blocks...

[anon]

There is function level try...catch which can also be around main.

It probably won't help, because if an unexpected exception is thrown (one that violates the exception specification) it won't reach the catch handler anyway.

I probably simply wouldn't use the throw specification if I don't know what exception might be thrown from the function.

------------

If either me or the OP misunderstand what unexpected is about, then yes catch all std::exception&'s in an outermost scope allows you to print what(), and catching ... just tells you that there was an exception.

[CornedBee]

You can #include <cxxabi.h> or something like that and call __cxa_get_exception_type() or something like that to get the type_info structure of the current exception. Then you can use this structure to get additional information - the same header contains information about how to do that.

The above is specific to compilers that implement the IA-64 C++ ABI: all compilers that run on Intel IA-64, as well as GCC and a few others everywhere.

[noobcpp]

Here In My Application the main job is done through an exec() method which is being called by main()
So I just put a try catch block around that exec() one

and It is workinf nicely.

[CornedBee]

What anon said is important, though. The unexpected handler is for exceptions that violated an exception specification. The handler you were looking for is the uncaught handler.