[uClibc 0000101]: Implementation of backtrace() from glibc would be useful
bugs at busybox.net
bugs at busybox.net
Sun Oct 7 23:35:50 UTC 2007
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=101
======================================================================
Reported By: hgb
Assigned To: uClibc
======================================================================
Project: uClibc
Issue ID: 101
Category: New Features
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
======================================================================
Date Submitted: 02-14-2005 02:09 PST
Last Modified: 10-07-2007 16:35 PDT
======================================================================
Summary: Implementation of backtrace() from glibc would be
useful
Description:
The backtrace() function (and its friends backtrace_symbols() and
backtrace_symbols_fd()) would be a very welcome addition to uClibc. I
have no idea how hard it is to implement, but if it's not-that-hard, I
would at least consider it a very useful addition. It is excellent for
debugging.
======================================================================
----------------------------------------------------------------------
enaess - 10-07-07 16:35
----------------------------------------------------------------------
Note for: uclibc-backtrace.tar.bz2
Hi,
I added backtrace support for uClibc 0.9.28 for both x86 and arm/xscale.
For the latter platform, you may need to tweak your compiler settings to
use -mapcs (arm procedure calling standard). This adds a bit overhead on a
per-function call basis but does the trick.
Have a nice day!
- Eivind
Issue History
Date Modified Username Field Change
======================================================================
02-14-05 02:09 hgb New Issue
03-16-05 11:55 andersen Assigned To andersen => uClibc
10-07-07 16:32 enaess File Added: uclibc-backtrace.tar.bz2
10-07-07 16:35 enaess Note Added: 0002813
======================================================================
More information about the uClibc-cvs
mailing list