Sponsored Content
Operating Systems Linux how to backtrace a shared library file (.so) Post 302240990 by frank_rizzo on Saturday 27th of September 2008 01:46:19 PM
Old 09-27-2008
1) not sure how you determine that

2) use the file command to determine bit width

file yourlib.so

you should be able to use the GNU debugger - gdb to get backtrace data
 

3 More Discussions You Might Find Interesting

1. AIX

How to debug a shared library(.so file) on AIX?

How to debug a shared library(.so file) on AIX? (1 Reply)
Discussion started by: AlbertGao
1 Replies

2. UNIX for Dummies Questions & Answers

What programs access shared library file

I was curious how to tell which programs are accessing a file (libobjc.A.dylib) in /usr/lib This file seems to be the culprit in a bunch of Safari crashes, and I just wanted to know if and what other programs use it. Also, I was curious what a good way to find out what files are being written... (4 Replies)
Discussion started by: glev2005
4 Replies

3. HP-UX

Problem in Shared library file .sl on 64bit HP-UX 11.11

We are facing issue with shared library file, we are getting difference in content for same shared file for chatr command :confused: , below are the detail about *.sl file, even we are also getting difference in size of both file. can you please tell me what will be the issue for same. is my new... (1 Reply)
Discussion started by: amodkavi
1 Replies
SDCDB(1)						      General Commands Manual							  SDCDB(1)

NAME
sdcdb - Source debugger for SDCC SYNOPSIS
sdcdb [options] filename WARNING
The information in this man page is an extract from the full documentation of SDCC, and is limited to the meaning of the options. For complete and current documentation, refer to the SDCC Compiler User Guide. DESCRIPTION
sdcdb is a source debugger for SDCC. It uses ucSim to execute the program, the programm execution is controlled by the debugger. The command interface for the debugger has been deliberately kept as close the GNU debugger gdb, as possible. This will help the integra- tion with existing graphical user interfaces (like ddd, xxgdb or xemacs) existing for the GNU debugger. STARTING THE DEBUGGER
The debugger can be started using the following command line (Assume the file you are debugging has the file name foo): sdcdb foo The debugger will look for the following files: foo.c - the source file. foo.cdb - the debugger symbol information file. foo.ihx - the intel hex format object file. OPTIONS
-directory=<source file directory> This option can used to specify the directory search list. The debugger will look into the directory list specified for source, cdb & ihx files. The items in the directory list must be separated by ':', e.g. if the source files can be in the directories /home/src1 and /home/src2, the -directory option should be -directory=/home/src1:/home/src2. Note there can be no spaces in the option. -cd <directory> Change to the <directory>. -fullname Used by GUI front ends. -cpu <cpu-type> This argument is passed to the simulator. Please see the simulator docs for details. -X <Clock frequency> This option is passed to the simulator. Please see the simulator docs for details. -s <serial port file> This option is passed to simulator. Please see the simulator docs for details. -S <serial in,out> This argument is passed to simulator. Please see the simulator docs for details. COPYING
The entire source code for the debugger is distributed under GNU General Public License. SEE ALSO
sdcc(1), ucsim(1), s51(1), savr(1), sz80(1). AUTHOR
This manual page was written by Aurelien Jarno <aurel32@debian.org>, for the Debian GNU/Linux system (but may be used by others). SDCDB(1)
All times are GMT -4. The time now is 10:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy