Backtrace Library 1.2.0 (Default branch)

Tags

Special Forums News, Links, Events and Announcements Software Releases - RSS News Backtrace Library 1.2.0 (Default branch)

01-12-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Backtrace Library 1.2.0 (Default branch)

Backtrace is a C library that replicates the btfunctionality from gdb. This can be used on codeas it is developed and on live code, to allowfunction stack tracing without having to run undergdb. This library will display the file name, function name, and line number in the backtrace, and will work even with a stripped binary.License: GNU General Public License (GPL)Changes:
This release brings forward a new site, new documentation including complete man pages, and some general tidying up and cleaning of the code.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. 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!

LEARN ABOUT DEBIAN

stg-publish

STG-PUBLISH(1)							   StGit Manual 						    STG-PUBLISH(1)

NAME

       stg-publish - Push the stack changes to a merge-friendly branch

SYNOPSIS

       stg publish [options] [branch]

DESCRIPTION

       This command commits a set of changes on a separate (called public) branch based on the modifications of the given or current stack. The
       history of the public branch is not re-written, making it merge-friendly and feasible for publishing. The heads of the stack and public
       branch may be different but the corresponding tree objects are always the same.

       If the trees of the stack and public branch are different (otherwise the command has no effect), StGit first checks for a rebase of the
       stack since the last publishing. If a rebase is detected, StGit creates a commit on the public branch corresponding to a merge between the
       new stack base and the latest public head.

       If no rebasing was detected, StGit checks for new patches that may have been created on top of the stack since the last publishing. If new
       patches are found and are not empty, they are checked into the public branch keeping the same commit information (e.g. log message, author,
       committer, date).

       If the above tests fail (e.g. patches modified or removed), StGit creates a new commit on the public branch having the same tree as the
       stack but the public head as its parent. The editor will be invoked if no "--message" option is given.

       It is recommended that stack modifications falling in different categories as described above are separated by a publish command in order
       to keep the public branch history cleaner (otherwise StGit would generate a big commit including several stack modifications).

       The public branch name can be set via the branch.<branch>.public configuration variable (defaulting to "<branch>.public").

OPTIONS

       -b BRANCH, --branch BRANCH
	   Use BRANCH instead of the default branch.

       --author "NAME <EMAIL>"
	   Set the author details.

       --authname NAME
	   Set the author name.

       --authemail EMAIL
	   Set the author email.

       --authdate DATE
	   Set the author date.

       -m MESSAGE, --message MESSAGE
	   Use MESSAGE instead of invoking the editor.

       -f FILE, --file FILE
	   Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)

       --sign
	   Add a "Signed-off-by:" to the end of the patch.

       --ack
	   Add an "Acked-by:" line to the end of the patch.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							    STG-PUBLISH(1)

Software Releases - RSS News