On Sun, 2006-07-30 at 18:48 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > The second bug causing spurious RT32 signals to be notified is more of a
> > GDB issue
>
> When running the attached program inside gdb, the RT32 signal seems to
> be used as the asynchronous cancellation
Philippe Gerum wrote:
> The second bug causing spurious RT32 signals to be notified is more of a
> GDB issue
When running the attached program inside gdb, the RT32 signal seems to
be used as the asynchronous cancellation signal. Or at least when
running with libthread_db.so.
--
On Fri, 2006-07-21 at 17:31 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
>
> > Jan Kiszka wrote:
> >
> >> Jan Kiszka wrote:
> >>
> >>> Hi,
> >>>
> >>> I stumbled over a strange behaviour of rt_task_delete for a created, set
> >>> periodic, but non-started task. The process gets killed on i
On Fri, 2006-07-21 at 17:31 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
>
> > Jan Kiszka wrote:
> >
> >> Jan Kiszka wrote:
> >>
> >>> Hi,
> >>>
> >>> I stumbled over a strange behaviour of rt_task_delete for a created, set
> >>> periodic, but non-started task. The process gets killed on i
Jan Kiszka wrote:
> Jan Kiszka wrote:
>
>> Jan Kiszka wrote:
>>
>>> Hi,
>>>
>>> I stumbled over a strange behaviour of rt_task_delete for a created, set
>>> periodic, but non-started task. The process gets killed on invocation,
>>>
>> More precisely:
>>
>> (gdb) cont
>> Program rece
Jan Kiszka wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> I stumbled over a strange behaviour of rt_task_delete for a created, set
>> periodic, but non-started task. The process gets killed on invocation,
>
> More precisely:
>
> (gdb) cont
> Program received signal SIG32, Real-time event 32.
>
> Weird.
Jan Kiszka wrote:
> Hi,
>
> I stumbled over a strange behaviour of rt_task_delete for a created, set
> periodic, but non-started task. The process gets killed on invocation,
More precisely:
(gdb) cont
Program received signal SIG32, Real-time event 32.
Weird. No kernel oops BTW.
> but only if r
