12-09-2013
Dbx not working on 64 bit Solaris machine
I have a 64 bit program called drivertest that crashed with the error message
Illegal Instruction (core dumped)
I tried to open the core file using dbx command bit it gives the below error message.
psrux902b1% dbx - core.drivertest.28276
Corefile specified executable: "/home/devops/drivertest/drivertest"
dbx: File `/home/devops/drivertest/drivertest' is not ELF executable
Isn't dbx supposed to work with 64 bit binaries?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How to change current working directory for dbx on UNIX?
means I'll run pgm from one directory , but getcwd() should return path which I want to be, which is not d current dir
:) (5 Replies)
Discussion started by: login0001
5 Replies
2. UNIX for Dummies Questions & Answers
There are two servers where my machine is connected. Is there any type of link formed between my machine and server machine? (1 Reply)
Discussion started by: palash2k
1 Replies
3. Red Hat
Hi all,
I'm looking to cover a corner case for an upcoming test cycle. Is there a way to boot a RedHat Advanced Server 4 (update 3) installed on a Power PC machine to use a 32 bit kernel? This would be similar to what is done here -> https://www.unix.com/aix/26204-aix-platform.html
I've done... (0 Replies)
Discussion started by: philrau
0 Replies
4. Solaris
I had previous implemented the following in my menu.lst to be able to get to 32-bit operations.
#
title Solaris 10 32-bit
root (hd0,0,a)
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
</code>
Now, it is not working as I get the following error :
... (0 Replies)
Discussion started by: praveenr
0 Replies
5. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
6. Linux
Hi,
I am using 32 bit machine, and I want to compile 64 bit application on 32-bit machine.
So please tell me is it possible or not?
Regards
Mandar (7 Replies)
Discussion started by: Mandar123
7 Replies
7. Solaris
hi,
I have some windows client machines which require a signal to be sent by a Solaris machine( SunOS 5.6) when ever a particular event occurs on that Solaris machine. What are possible communication mechanisms by which i can do this.
the constraints are
> the windows machines have to... (7 Replies)
Discussion started by: Krsh
7 Replies
8. Solaris
:confused:
how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6.
also i want to know the difference between 32 bit and 64bit os.
any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies
9. IP Networking
This is probably really basic compared to what you guys are usually talking about here, but I have a problem and I have no idea what to do about it. I try to RSH to my Ubuntu computer from my Solaris one and run into a dead end:
>> rsh 192.168.1.103
::ffff:192.168.1.103: Connection timed out... (4 Replies)
Discussion started by: Bradj47
4 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Below is the sample file:
$ cat x.txt
MDSYS|OGIS_GEOMETRY_COLUMNS|TABLE
MDSYS|OGIS_SPATIAL_REFERENCE_SYSTEMS|TABLE
MDSYS|SDO_IDX_TAB_SEQUENCE|SEQUENCE
MDSYS|SDO_PREFERRED_OPS_USER|TABLE
MDSYS|SDO_ST_TOLERANCE|TABLE
MDSYS|SDO_TOPO_DATA$|TABLE
MDSYS|SDO_TOPO_RELATION_DATA|TABLE... (4 Replies)
Discussion started by: newbie_01
4 Replies
LEARN ABOUT DEBIAN
btraceback
BTRACEBACK(1) Network backup, recovery and verification BTRACEBACK(1)
NAME
btraceback - wrapper script around gdb and bsmtp
SYNOPSIS
btraceback /path/to/binary pid
DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.
USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur-
rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).
NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.
Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse-
quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.
ENVIRONMENT
btracback relies on $PATH to find the debugger.
FILES
/usr/lib/bacula/btraceback
The script itself.
/usr/sbin/btraceback
symbolic link to /usr/lib/bacula/btraceback
/etc/bacula/scripts/btraceback.gdb
the GDB command batch used to output a stack trace
AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>
SEE ALSO
bsmtp(1)
Kern Sibbald 6 December 2009 BTRACEBACK(1)