Figure out source of SIGXCPU signals.

flybeyond / atrias

Automatically exported from code.google.com/p/atrias

0 stars 0 forks source link

Figure out source of SIGXCPU signals. #93

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

During startup, we're getting unwarranted SIGXCPU signals. We need to find out 
their source (possibly Orocos itself) and fix this.

Original issue reported on code.google.com by jrvanwhy on 30 Aug 2012 at 5:06

GoogleCodeExporter commented 9 years ago

These signals are becoming bothersome for debugging... bumping issue priority.

Original comment by jrvanwhy on 7 Sep 2012 at 3:38

Added labels: Priority-Medium
Removed labels: Priority-Low

GoogleCodeExporter commented 9 years ago

I'm beginning work on this now. It's more important than everything else, 
except for completing the Medulla drivers.

Original comment by jrvanwhy on 11 Sep 2012 at 5:39

Changed state: Started
Added labels: Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

I don't have any ideas on this one. Could someone else help?

Original comment by jrvanwhy on 11 Sep 2012 at 5:59

GoogleCodeExporter commented 9 years ago

I've spent some more time emailing the Orocos-users list... it does not seem 
reproducible. Closing, since this does not seem to be fixable on our end.

Original comment by jrvanwhy on 29 Oct 2012 at 4:58

Changed state: WontFix