Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-17 Thread Philippe Gerum
Jan Kiszka wrote: Philippe Gerum wrote: Jan Kiszka wrote: Philippe Gerum wrote: Jan Kiszka wrote: Philippe, do you see any remaining issues, e.g. that the leak survived the task termination? Does this have any meaning for correct driver and skin code? The only way I could see this le

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-17 Thread Jan Kiszka
Philippe Gerum wrote: > Jan Kiszka wrote: >> Philippe Gerum wrote: >> >>> Jan Kiszka wrote: >>> >> Philippe, do you see any remaining issues, e.g. that the leak >> survived >> the task termination? Does this have any meaning for correct >> driver and >> skin code? >> > >

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-16 Thread Philippe Gerum
Jan Kiszka wrote: Philippe Gerum wrote: Jan Kiszka wrote: Philippe, do you see any remaining issues, e.g. that the leak survived the task termination? Does this have any meaning for correct driver and skin code? The only way I could see this leakage survive a switch transition would requir

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Philippe Gerum
Jan Kiszka wrote: Philippe Gerum wrote: Jan Kiszka wrote: Philippe, do you see any remaining issues, e.g. that the leak survived the task termination? Does this have any meaning for correct driver and skin code? The only way I could see this leakage survive a switch transition would requir

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Jan Kiszka
Philippe Gerum wrote: > Jan Kiszka wrote: Philippe, do you see any remaining issues, e.g. that the leak survived the task termination? Does this have any meaning for correct driver and skin code? >>> >>> The only way I could see this leakage survive a switch transition woul

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Philippe Gerum
Jan Kiszka wrote: Philippe, do you see any remaining issues, e.g. that the leak survived the task termination? Does this have any meaning for correct driver and skin code? The only way I could see this leakage survive a switch transition would require it to happen over the root context, not o

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Jan Kiszka
Philippe Gerum wrote: > Jan Kiszka wrote: >> Jan Kiszka wrote: >> >>> Jan Kiszka wrote: >>> Hi Philippe, debugging is nice, tracing is still nicer. As you suggested, I extended the tracer with per-domain stall flags (needs some output clean-up, preliminary patch attached ne

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Philippe Gerum
Jan Kiszka wrote: Jan Kiszka wrote: Jan Kiszka wrote: Hi Philippe, debugging is nice, tracing is still nicer. As you suggested, I extended the tracer with per-domain stall flags (needs some output clean-up, preliminary patch attached nevertheless). And here is the result (full trace attache

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-10 Thread Jan Kiszka
Jan Kiszka wrote: > Jan Kiszka wrote: >> Hi Philippe, >> >> debugging is nice, tracing is still nicer. As you suggested, I extended >> the tracer with per-domain stall flags (needs some output clean-up, >> preliminary patch attached nevertheless). >> >> And here is the result (full trace attached):

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-09 Thread Philippe Gerum
Jan Kiszka wrote: Jan Kiszka wrote: Hi Philippe, debugging is nice, tracing is still nicer. As you suggested, I extended the tracer with per-domain stall flags (needs some output clean-up, preliminary patch attached nevertheless). And here is the result (full trace attached): :|(0x51)

Re: [Xenomai-core] [BUG?] stalled xeno domain

2006-04-08 Thread Jan Kiszka
Jan Kiszka wrote: > Hi Philippe, > > debugging is nice, tracing is still nicer. As you suggested, I extended > the tracer with per-domain stall flags (needs some output clean-up, > preliminary patch attached nevertheless). > > And here is the result (full trace attached): > >> :|(0x51) 0x000

[Xenomai-core] [BUG?] stalled xeno domain

2006-04-08 Thread Jan Kiszka
Hi Philippe, debugging is nice, tracing is still nicer. As you suggested, I extended the tracer with per-domain stall flags (needs some output clean-up, preliminary patch attached nevertheless). And here is the result (full trace attached): > :|(0x51) 0x00c8 -1113+ 1.112 __ipipe_sync_