08-08-2008
MIPS backtrace
Hi,
I'm working in a MIPS processor and, since the function backtrace() is not implemented for this architecture, I would like to know if there is another way to do a stack backtrace in this processor.
Thanks a lot!!!
6 More Discussions You Might Find Interesting
1. Programming
i need to know how one can get the backtrace of a program in c++
as you find in gdb or dbx on doing a ctrl c (or any signal to the os)
do help (6 Replies)
Discussion started by: wojtyla
6 Replies
2. Programming
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Discussion started by: dmirza
2 Replies
3. Linux
I have a shared library file (.so) and I need to know some information
1. By which GCC version was this .so built?
2. Was this .so built in 32 bits mode or 64 bits mode
Any command / tools to backtrace such kind of information?
Thanks in advance! (2 Replies)
Discussion started by: princelinux
2 Replies
4. UNIX for Dummies Questions & Answers
Does anyone know if there is a pkg for installing cron on a mips processor machine with embedded linux? (0 Replies)
Discussion started by: Trogman
0 Replies
5. UNIX and Linux Applications
Hi All,
I am trying to cross compile udev-151 for MIPS little endian architecture.
I am configuring like this:
./configure --prefix=$PWD/sree --host=mips-linux-gnu
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then... (3 Replies)
Discussion started by: bsreeram
3 Replies
6. Programming
Hi, all
I try to understand the output from gdb
Program received signal SIGABRT, Aborted.
*** glibc detected *** /home/sys_cbo/dev/zif/bin/Debug/zifd: free(): invalid pointer: 0x00007fffac04d3d0 ***
how should i read this?
(gdb) backtrace
#0 0x0000003015e32925 in raise () from... (1 Reply)
Discussion started by: huvcbo
1 Replies
LEARN ABOUT MOJAVE
backtrace
backtrace(3) BSD Library Functions Manual backtrace(3)
NAME
backtrace, backtrace_symbols, backtrace_symbols_fd -- call stack backtrace and display functions
SYNOPSIS
#include <execinfo.h>
int
backtrace(void** array, int size);
char**
backtrace_symbols(void* const* array, int size);
void
backtrace_symbols_fd(void* const* array, int size, int fd);
DESCRIPTION
These routines provide a mechanism to examine the current thread's call stack.
backtrace() writes the function return addresses of the current call stack to the array of pointers referenced by array. At most, size
pointers are written. The number of pointers actually written to array is returned.
backtrace_symbols() attempts to transform a call stack obtained by backtrace() into an array of human-readable strings using dladdr(). The
array of strings returned has size elements. It is allocated using malloc() and should be released using free(). There is no need to free
the individual strings in the array.
backtrace_symbols_fd() performs the same operation as backtrace_symbols(), but the resulting strings are immediately written to the file
descriptor fd, and are not returned.
EXAMPLE
#include <execinfo.h>
#include <stdio.h>
...
void* callstack[128];
int i, frames = backtrace(callstack, 128);
char** strs = backtrace_symbols(callstack, frames);
for (i = 0; i < frames; ++i) {
printf("%s
", strs[i]);
}
free(strs);
...
HISTORY
These functions first appeared in Mac OS X 10.5.
SEE ALSO
dladdr(3), malloc(3)
Mac OS X February 15, 2007 Mac OS X