[En-Nut-Discussion] Re: [btnode-development] Bug in timer.c?

[Matthias Ringwald]

hi ole

I've just discovered the Bug that Lukas spottet. Stay tuned, more on  
this in half an hour.

Btw. I don't know if the unix emulation is working properly since the  
changes to
the new timer irq handling. Maybe you want to do a code review on the  
unix timer handling?

Besides, you even get an error msg. Will have a look at this later.

Matthias

On 12.07.2005, at 15:09, Ole Reinhardt wrote:

> ..
> I use the unix emulation, but I suppose this also could happen with  
> the
> avr code?
>
> That the gdb output:
>
> [rfcomm-cmd]$inquiry sync
> Starting sync inquiry for 5 sec:
> Devices: 1
> Device         bt_addr cod        RSSI
> [0]: 00:02:72:40:42:b0 0x003e0100 0
> [rfcomm-cmd]$rfsession 0 1
> RFCOMM connect to 00:02:72:40:42:b0 Channel 1
> L2CAP:Created connection for handle: 1 at index 0
> RFCOMM: L2CAP connect . Unique handle: 0021
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1260528720 (LWP 18658)]
> 0x0804a77b in NutTimerProcessElapsed () at timer.c:324
> 324                     nexttn->tn_next->tn_ticks_left +=
> nexttn->tn_ticks_left;(gdb) bt
> #0  0x0804a77b in NutTimerProcessElapsed () at timer.c:324