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
gcore(1) BSD General Commands Manual gcore(1)
NAME
gcore -- get core images of running processes
SYNOPSIS
gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid
DESCRIPTION
The gcore program creates a core file image of the process specified by pid. The resulting core file can be used with a debugger, e.g.
lldb(1), to examine the state of the process.
The following options are available:
-s Suspend the process while the core file is captured.
-v Report progress on the dump as it proceeds.
-b size Limit the size of the core file to size MiBytes.
The following options control the name of the core file:
-o path
Write the core file to path.
-c pathformat
Write the core file to pathformat. The pathformat string is treated as a pathname that may contain various special characters which
cause the interpolation of strings representing specific attributes of the process into the name.
Each special character is introduced by the % character. The format characters and their meanings are:
N The name of the program being dumped, as reported by ps(1).
U The uid of the process being dumped, converted to a string.
P The pid of the process being dumped, converted to a string.
T The time when the core file was taken, converted to ISO 8601 format.
% Output a percent character.
The default file name used by gcore is %N-%P-%T. By default, the core file will be written to a directory whose name is determined from the
kern.corefile MIB. This can be printed or modified using sysctl(8).
The directory where the core file is to be written must be accessible to the owner of the target process.
gcore will not overwrite an existing file, nor will it create missing directories in the path.
EXIT_STATUS
The gcore utility exits 0 on success, and >0 if an error occurs.
FILES
/cores/%N-%P-%T default pathname for the corefile.
BUGS
With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image. Such
a partial core dump may confuse subsequent programs that attempt to parse the contents of such files.
SEE ALSO
lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8).
Darwin May 31, 2019 Darwin