Date: Fri, 4 Jan 2013 12:38:44 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Stefan Farfeleder <stefanf@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Unbreaking gdb's catch throw Message-ID: <FC255095-1EFB-4713-887E-E79C53C9F193@FreeBSD.org> In-Reply-To: <20130104123424.GA1430@mole.fafoe.narf.at> References: <20130104123424.GA1430@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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 __cxa_throw itself, then it should tell you that there = are multiple definitions and ask which one you want (if it doesn't, it's = a gdb bug). =20 David On 4 Jan 2013, at 12:34, Stefan Farfeleder wrote: > Hi, >=20 > 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. >=20 > Stefan > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FC255095-1EFB-4713-887E-E79C53C9F193>