| To: | Ethan Solomita <ethan@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: user-mode debugging |
| From: | Keith Owens <kaos@xxxxxxx> |
| Date: | Fri, 07 Jun 2002 12:02:42 +1000 |
| Cc: | "Van Maren, Kevin" <kevin.vanmaren@xxxxxxxxxx>, "'kdb@xxxxxxxxxxx'" <kdb@xxxxxxxxxxx>, "'David Mosberger'" <davidm@xxxxxxxxxxxxxxxxx> |
| In-reply-to: | Your message of "Thu, 06 Jun 2002 16:23:53 MST." <3CFFEF09.4010704@cs.columbia.edu> |
| Sender: | owner-kdb@xxxxxxxxxxx |
On Thu, 06 Jun 2002 16:23:53 -0700, Ethan Solomita <ethan@xxxxxxxxxxxxxxx> wrote: > You should be able to get the user's registers from "rd u". Then you > can >see about doing the backtrace by hand. Is it possible to find a stack >frame pointer for the user space, and then pass it in as an argument to >"bt"? User space stack frames require a process context to access them. kdb runs out of interrupt context, accessing user space is fragile at best. bt on ia64 needs the unwind data and kdb has no idea where that is for user space, it only knows about kernel unwind data. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: user-mode debugging, Ethan Solomita |
|---|---|
| Next by Date: | Re: Line numbers in kdb?, Keith Owens |
| Previous by Thread: | Re: user-mode debugging, Ethan Solomita |
| Next by Thread: | USB Keyboard in KDB - patch for kernel 2.4.18, LELARGE Sebastien |
| Indexes: | [Date] [Thread] [Top] [All Lists] |