[Rock-dev] Orocos silently swallows exceptions
Peter Soetens
peter at thesourceworks.com
Fri Feb 11 12:12:37 CET 2011
On Friday 11 February 2011 11:23:35 Sylvain Joyeux wrote:
> On 02/11/2011 10:32 AM, Jakob Schwendner wrote:
> > Hi,
> >
> > this is the second time, I ran into the problem, that I suspected Orocos
> > to silently swallow exceptions.
> > This time I traced it down to RTT (rtt/ExecutionEngine.cpp).
> >
> > // A trigger() in startHook() will be ignored, we trigger in TaskCore
> > after startHook finishes.
> >
> > if ( taskc->mTaskState == TaskCore::Running&&
> >
> > taskc->mTargetState == TaskCore::Running ) {
> >
> > try {
> >
> > taskc->prepareUpdateHook();
> > taskc->updateHook();
> >
> > } catch(...){
> >
> > taskc->exception(); // calls stopHook,cleanupHook
> >
> > }
> >
> > }
> >
> > fair enough it catches my exception, but shouldn't it let me know about
> > it? Is there something I missed?
>
> No, but there was something I missed. I added log lines for hooks in
> TaskCore and did not realize that updateHook() and errorHook() were not
> covered. Will fix.
Hi Sylvain,
Could you clarify what these log lines are ?
Peter
More information about the Rock-dev
mailing list