Re: Task context information available on crash

2018-03-20 Thread Sebastian Huber
On 20/03/18 11:49, Matthew J Fletcher wrote: Thank you for the advice. So i can see that the executing task was "TIME", which is the timer server. So the problem is almost certainly a bad function pointer passed as the routine to invoke. I can place a breakpoint in timerserver.c, but the cra

Re: Task context information available on crash

2018-03-20 Thread Matthew J Fletcher
Thank you for the advice. So i can see that the executing task was "TIME", which is the timer server. So the problem is almost certainly a bad function pointer passed as the routine to invoke. I can place a breakpoint in timerserver.c, but the crash is after several minutes (and many tens of thou

Re: Task context information available on crash

2018-03-19 Thread Sebastian Huber
On 19/03/18 18:36, Matthew J Fletcher wrote: Hi, When an application crashes and the bsp_fatal_extension() is invoked, is there a way to see (in gdb or otherwise) what the last executing task was ? I guess there is some task context maintained but it would be internal to rtems. You can ge

Re: Task context information available on crash

2018-03-19 Thread Chris Johns
On 20/03/2018 04:36, Matthew J Fletcher wrote: > > When an application crashes and the bsp_fatal_extension() is invoked, is > there a > way to see (in gdb or otherwise) what the last executing task was ? > > I guess there is some task context maintained but it would be internal to > rtems. >