As "catch throw" is not yet working in the current (5.3) gdb you can use

break __cxa_throw

to achieve the same result - eg for checking the stack trace. No really a POOL issue, but as POOL exceptions tend to be not very explicit yet, this may help to obtain the exception context.

We are revisiting proper exception handling including building up a proper exception context for diagnostics as part of POOL V1.0.

Also see fro details :