On 2013-01-04 14:02, Stefan Farfeleder wrote:
On Fri, Jan 04, 2013 at 12:54:03PM +, David Chisnall wrote:
As a work-around, you can put the breakpoint on _Unwind_RaiseException instead.
This will work for any language, not just C++ (e.g. it will notice Objective-C
or gcj-compiled Java exc
On Fri, Jan 04, 2013 at 12:54:03PM +, David Chisnall wrote:
>
> As a work-around, you can put the breakpoint on _Unwind_RaiseException
> instead. This will work for any language, not just C++ (e.g. it will notice
> Objective-C or gcj-compiled Java exceptions).
>
Thank you, that works for
On 4 Jan 2013, at 12:49, Stefan Farfeleder wrote:
> On Fri, Jan 04, 2013 at 12:38:44PM +, David Chisnall wrote:
>> Is this on 9.1? In -CURRENT and 9.1, libstdc++ is a filter library, and
>> libsupc++ or or libcxxrt are the filtee. This means that the __cxa_throw
>> symbol appears to be in
On Fri, Jan 04, 2013 at 12:38:44PM +, David Chisnall wrote:
> Is this on 9.1? In -CURRENT and 9.1, libstdc++ is a filter library, and
> libsupc++ or or libcxxrt are the filtee. This means that the __cxa_throw
> symbol appears to be in libstdc++ (for symbol versioning purposes), but is
> ac
Stefan Farfeleder wrote:
> gdb's command 'catch throw' is broken on FreeBSD head. While it does set
> a breakpoint on __cxa_throw, the function seems to be never entered when
> an exception is thrown. Does someone know how to fix this? It used to
> work a couple of months ago.
My impression is t
Is this on 9.1? In -CURRENT and 9.1, libstdc++ is a filter library, and
libsupc++ or or libcxxrt are the filtee. This means that the __cxa_throw
symbol appears to be in libstdc++ (for symbol versioning purposes), but is
actually in the ABI library. If you tell gdb to put the breakpoint on
__
Hi,
gdb's command 'catch throw' is broken on FreeBSD head. While it does set
a breakpoint on __cxa_throw, the function seems to be never entered when
an exception is thrown. Does someone know how to fix this? It used to
work a couple of months ago.
Stefan
_