pussuw commented on code in PR #10858:
URL: https://github.com/apache/nuttx/pull/10858#discussion_r1346240310
##########
sched/misc/assert.c:
##########
@@ -554,12 +554,22 @@ static void dump_deadlock(void)
void _assert(FAR const char *filename, int linenum,
FAR const char *msg, FAR void *regs)
{
- FAR struct tcb_s *rtcb = running_task();
+ FAR struct tcb_s *rtcb = current_task();
Review Comment:
Ok thanks for the explanation. There is some other bug then, because when
e.g. a page fault from user space occurs, running_task() never points to the
user space thread that faulted but rather to a high priority kernel task (maybe
a context switch is happening too). This info to me is useless, which is why I
changed to "current_task" which gives the correct user space thread.
Need to find what the issue is, reverting this change.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
