From: David Daney <ddaney@avtrex.com>
To: Sudeep Kottilingal <skottilingal@kinetowireless.com>
Cc: linux-mips@linux-mips.org,
Joe Baranowski <jbaranowski@kinetowireless.com>
Subject: Re: Backtrace capability
Date: Tue, 30 Sep 2003 12:14:55 -0700 [thread overview]
Message-ID: <3F79D62F.5070901@avtrex.com> (raw)
In-Reply-To: <2EEAE99C5AA0B14BB6A0BBB4ABF8D1E117960E@blunote.bluzona.com>
Sudeep Kottilingal wrote:
> Hi all,
>
> I am trying to debug some SIGSEGV when I leave my system ON for a few
> days. At the time of the
>
> Crash I am not able to get a nice back-trace/stack trace yet. (I do
> not see the execinfo.h file on my uclibc toolchain
>
> Which implies its not supported yet on my toolchain release).
>
> *Has anyone had success in incorporating backtrace capability into a
> uclibc binary yet …?*
>
> *If your answer is yes, could u give me some pointers on how to do it
> and set it up ..?*
>
> *If your answer is no is there any other alternative set up to get
> more information.*
>
> I do not run an ICD or ICE on my board. Neither do I have a serial
> console. My console is redirected via Telnet.
>
> Currently I am running the application which crashes on the linux PC
> through totalview debugger.
>
> Waiting for it to crash.
>
> sudeep
>
I hacked together a backtrace that you may be able to adapt. It was
originally for gcj, but we use several variations for other things as
well. It kind of relies on an o32 ABI calling convention.
The code is in this mail message:
http://gcc.gnu.org/ml/java-patches/2003-q3/msg00584.html
Look at:
libjava/sysdep/mips/mipsel-backtracer.c
libjava/sysdep/mips/mipsel-backtracer.h
libjava/sysdep/mips/mipsel-bthelper.S
David Daney
prev parent reply other threads:[~2003-09-30 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 18:37 Backtrace capability Sudeep Kottilingal
2003-09-30 18:37 ` Sudeep Kottilingal
2003-09-30 19:14 ` David Daney [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=3F79D62F.5070901@avtrex.com \
--to=ddaney@avtrex.com \
--cc=jbaranowski@kinetowireless.com \
--cc=linux-mips@linux-mips.org \
--cc=skottilingal@kinetowireless.com \
/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