On 05/31/2013 09:33 PM, Tom Tromey wrote:
Tom I think it may be fixable in GCC.
I filed a GCC bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57487
You can CC yourself on it if you want to see what happens.
Great, thanks. (So your idea would be to, in a second step, teach ABRT
to
Stephan == Stephan Bergmann sberg...@redhat.com writes:
Stephan Great, thanks. (So your idea would be to, in a second step, teach
Stephan ABRT to issue additional gdb commands besides backtrace in case the
Stephan trace contains __gnu_cxx::__verbose_terminate_handler, right?)
If that GCC bug
On 06/03/2013 04:36 PM, Tom Tromey wrote:
Stephan == Stephan Bergmann sberg...@redhat.com writes:
Stephan Great, thanks. (So your idea would be to, in a second step, teach
Stephan ABRT to issue additional gdb commands besides backtrace in case the
Stephan trace contains
Tom I think it may be fixable in GCC.
I filed a GCC bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57487
You can CC yourself on it if you want to see what happens.
Tom
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
On 02/20/2013 10:28 PM, Tom Tromey wrote:
FWIW we have the same problem in reverse: the gdb group at Red Hat is,
among other things, tasked with improving the C++ debugging experience.
However, most of us don't actually debug C++ programs on a regular
basis. We do know some issues, via bugzilla
Stephan == Stephan Bergmann sberg...@redhat.com writes:
Stephan It would be cool if there were a way to see that message in the gdb
Stephan backtrace. Like __gnu_cxx::__verbose_terminate_handler assembling the
Stephan message and then calling a not-optimized-away helper function with the
Tom I think it isn't possible in general. When an exception is thrown, I
Tom think all that can really be determined is the next catch point.
Michael This would be perfect. Explicit rethrows are relatively rare in
Michael our code, however it is completely normal to have code that we
Michael
Hi Tom,
On Tue, 2013-02-26 at 14:23 +0100, Jan Holesovsky wrote:
Michael Even better than this would (perhaps) be a break inside thrower
that
Michael is caught here type breakpoint - that we could invoke to land us
in
Michael whatever code is going to throw as it does that [ and
Tom == Tom Tromey tro...@redhat.com writes:
Tom The various low-level exception-related functions, like __cxa_throw,
Tom treat the exception object as a void *. However, the value of this
Tom seems to change depending on the throw point. It's clear that this
Tom can't always be the argument to
On 02/22/2013 07:14 PM, Tom Tromey wrote:
I'm curious what types of exceptions are actually thrown in LibreOffice.
Does it throw -- scalars? Objects? Just pointers (Java style)?
LibreOffice's UNO component system has a large exception hierarchy,
which is modeled as a hierarchy of classes in
Hi Tom,
Tom Tromey píše v Pá 22. 02. 2013 v 11:14 -0700:
Michael Even better than this would (perhaps) be a break inside thrower that
Michael is caught here type breakpoint - that we could invoke to land us in
Michael whatever code is going to throw as it does that [ and before it
started
Hi Tom,
On Wed, 2013-02-20 at 14:28 -0700, Tom Tromey wrote:
FWIW we have the same problem in reverse: the gdb group at Red Hat is,
among other things, tasked with improving the C++ debugging experience.
However, most of us don't actually debug C++ programs on a regular
basis. We do know
Michael == Michael Meeks michael.me...@suse.com writes:
Michael The basic debugging experience in these an exception broke
Michael something flows is that we get an exception thrown that
Michael ultimately ends up in a pathalogical situation - an abort, or
Michael some similar horrible badness.
Lubos == Lubos Lunak l.lu...@suse.cz writes:
Tom Is there something we could do to improve it?
Lubos I don't know how much control gdb over exception handling has,
Lubos so I don't know :).
:-)
FWIW we have the same problem in reverse: the gdb group at Red Hat is,
among other things, tasked
On Monday 18 of February 2013, Tom Tromey wrote:
Lubos == Lubos Lunak l.lu...@suse.cz writes:
Lubos This could be very useful ('catch throw' is so cumbersome in
Lubos gdb),
Is there something we could do to improve it?
I don't know how much control gdb over exception handling has, so I
15 matches
Mail list logo
