From: Hui Zhu <teawater@gmail.com>
To: Michael Eager <eager@eagerm.com>
Cc: gdb@sourceware.org
Subject: Re: Backtrace from kernel to user space in coredump
Date: Mon, 14 Jun 2010 07:23:00 -0000 [thread overview]
Message-ID: <AANLkTimDGda6_JKMbcV3d76xRYPi0yqPnSFZJ4zgQe36@mail.gmail.com> (raw)
In-Reply-To: <4C138642.2080202@eagerm.com>
http://sourceware.org/ml/gdb-patches/2010-02/msg00533.html
I make this patch for other thing. It can save the memory and reg
operation command's value and send it to GDB as the inferior's value.
Then you can do backtrace.
I think maybe you can put the reg and sp memory 's value to GDB. Then
you can do backtrace.
Thanks,
Hui
On Sat, Jun 12, 2010 at 21:06, Michael Eager <eager@eagerm.com> wrote:
> Hi --
>
> I want to be able to generate a backtrace in a
> core dump from a uClinux kernel routine (say,
> do_trap() or do_page_fault()) to the user-space
> routine which caused the trap. The kernel function
> is called with a pt_regs struct which contains the
> user regs.
>
> One way I thought to do this is to set the $PC and
> $SP to the value saved in pt_regs and do a "bt".
> If I try to set the $PC, gdb complains that there
> is no process, since there are no routines to modify
> a core file.
>
> I can modify gdb to save the registers returned from
> reading the core file and add routines allow modifying
> these saved register values.
>
> Are there better ways to do this? How have other
> people handled traces back from kernel to user space?
>
>
> --
> Michael Eager eager@eagercon.com
> 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
>
prev parent reply other threads:[~2010-06-14 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 13:06 Michael Eager
2010-06-12 15:19 ` Frédéric RISS
2010-06-12 16:16 ` Paul Koning
2010-06-14 3:18 ` Michael Eager
2010-06-14 7:23 ` Hui Zhu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimDGda6_JKMbcV3d76xRYPi0yqPnSFZJ4zgQe36@mail.gmail.com \
--to=teawater@gmail.com \
--cc=eager@eagerm.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox