Sponsored Content
Full Discussion: BackTrace
Top Forums Programming BackTrace Post 85020 by wojtyla on Friday 30th of September 2005 08:00:47 AM
Old 09-30-2005
Question BackTrace

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
 

4 More Discussions You Might Find Interesting

1. Programming

printing a stack trace with backtrace

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

2. Linux

how to backtrace a shared library file (.so)

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

3. Programming

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!!! (3 Replies)
Discussion started by: lagigliaivan
3 Replies

4. Programming

Gdb backtrace

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
GZEXE(1)						      General Commands Manual							  GZEXE(1)

NAME
gzexe - compress executable files in place SYNOPSIS
gzexe name ... DESCRIPTION
The gzexe utility allows you to compress executables in place and have them automatically uncompress and execute when you run them (at a penalty in performance). For example if you execute ``gzexe /usr/bin/gdb'' it will create the following two files: -rwxr-xr-x 1 root root 1026675 Jun 7 13:53 /usr/bin/gdb -rwxr-xr-x 1 root root 2304524 May 30 13:02 /usr/bin/gdb~ /usr/bin/gdb~ is the original file and /usr/bin/gdb is the self-uncompressing executable file. You can remove /usr/bin/gdb~ once you are sure that /usr/bin/gdb works properly. This utility is most useful on systems with very small disks. OPTIONS
-d Decompress the given executables instead of compressing them. SEE ALSO
gzip(1), znew(1), zmore(1), zcmp(1), zforce(1) CAVEATS
The compressed executable is a shell script. This may create some security holes. In particular, the compressed executable relies on the PATH environment variable to find gzip and some standard utilities (basename, chmod, ln, mkdir, mktemp, rm, sleep, and tail). BUGS
gzexe attempts to retain the original file attributes on the compressed executable, but you may have to fix them manually in some cases, using chmod or chown. GZEXE(1)
All times are GMT -4. The time now is 11:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy