Opened 8 years ago

Last modified 2 years ago

#7862 assigned bug

dropping the running team in KDL recursively enters KDL

Reported by: pulkomandy Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

  • Crash an application
  • enter KDL to kill it
  • use drop nnn, where nnn is the currently running team
  • notice the error
  • you now have to type co twice to get out of KDL ! That's confusing at best :)

Change History (4)

comment:1 Changed 8 years ago by bonefish

First of all, any kernel debugger command that modifies the state of the system in inherently unsafe. So, if you use one of those, you do that at your own peril. The drop command is particularly unsafe and I recently tagged it with a respective TODO. IMO it is also a relatively useless command, since there are several ways to drop a thread into the debugger from userland (PC or just attaching a debugger).

The need for typing co twice is actually not confusing at all. One is needed to leave the panic state the drop command triggered. The second is to leave KDL.

comment:2 Changed 8 years ago by axeld

I don't see that much use in this command (suspending a thread from the kernel would be enough even to stop ill doing real time threads), so I guess we could just drop it, and be safe again.

comment:3 Changed 4 years ago by pulkomandy

Milestone: R1Unscheduled

comment:4 Changed 2 years ago by axeld

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.