[Paraview] exception handler
Mattijs Janssens
m.janssens at opencfd.co.uk
Thu May 29 10:24:14 EDT 2008
No it still rethrows from the same position.
#5 0x00002ae5ce661ce5 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#6 0x00002ae5bf32e9b5 in QEventLoop::exec (this=0x7fffef488870,
flags=@0x7fffef488880) at kernel/qeventloop.cpp:205
#7 0x00002ae5bf33096e in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:845
On Thursday 29 May 2008 14:42, Moreland, Kenneth wrote:
> I get that a lot in ParaView when my code is doing an incorrect memory
> access (seg fault, bus error, etc.). Try running ParaView in a debugger
> and see if it breaks on the real problem.
>
> -Ken
>
> > -----Original Message-----
> > From: paraview-bounces at paraview.org
> > [mailto:paraview-bounces at paraview.org] On Behalf Of Mattijs Janssens
> > Sent: Thursday, May 29, 2008 6:40 AM
> > To: paraview at paraview.org
> > Subject: [Paraview] exception handler
> >
> > Hello all,
> >
> > from my reader module I get the message below. Excellent message and am
> > probably doing something wrong but how do I find out which routine in my
> > reader is the culprit? gdb on the core just tells me that it is inside
> > QEventLoop::exec.
> >
> > "Qt has caught an exception thrown from an event handler. Throwing
> > exceptions from an event handler is not supported in Qt. You must
> > reimplement QApplication::notify() and catch all exceptions there.
> >
> > terminate called after throwing an instance of 'std::length_error'
> > what(): basic_string::_S_create
> > "
> >
> > Regards,
> >
> > Mattijs
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
--
Mattijs Janssens
OpenCFD Ltd.
9 Albert Road,
Caversham,
Reading RG4 7AN.
Tel: +44 (0)118 9471030
Email: M.Janssens at OpenCFD.co.uk
URL: http://www.OpenCFD.co.uk
More information about the ParaView
mailing list