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
core(4) Kernel Interfaces Manual core(4)
NAME
core - Format of memory image file
SYNOPSIS
#include <sys/core.h>
DESCRIPTION
The system writes out a memory image of a terminated process when any of various errors occur. See sigaction(2) for the list of reasons;
the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called core
and is written in the process's working directory (provided that it can be; normal access controls apply).
The maximum size of a core file is limited. If a process exceeds this limit, any remaining data to be written to the core file is lost.
Default behavior is for the system to create a file named core, overwriting any other file with that name in the working directory.
You can enable enhanced core file naming, which causes the system to create unique names for core files. Core files are not overwritten,
thereby preventing loss of valuable debugging information when the same program fails mulitiple times (and perhaps for mulitple reasons).
When enhanced core file naming is enabled, the system produces core files with names in the following format:
core.program_name.host_name.numeric_tag The literal string core. Up to sixteen characters taken from the program name as shown by the ps
command. The first portion of the system's network host name, or up to 16 characters of the host name, taken from the part of the host
name that precedes the first dot. This tag is assigned to the core file to make it unique among all of the core files generated by a pro-
gram on a host. The maximum value for this tag, and thus the maximum number of core files for this program and host, is set by a system
configuration parameter.
Note the tag is not a literal version number. The system selects the first available unique tag for the core file. For example, if a
program's core files have tags .0, .1, and .3, the system uses tag .2 for the next core file it creates for that program. If the
system-configured limit for core file instances is reached, the system will not create any more core files for that program/host
combination. By default, the system can create up to 16 versions of a core file.
For example, the fourth core file generated on host buggy.net.ooze.com by the program dropsy would be: core.dropsy.buggy.3
Enhanced core file naming can be enabled at the system level or the program level: At the system level, you can enable enhanced core file
naming by setting the enhanced-core-name system configuration variable to 1 in the proc subsystem: proc:
enhanced-core-name = 1 At the program level, you can enable enhanced core file naming by calling the uswitch system call with the
USW_CORE flag set. See the EXAMPLE section.
The system manager can limit the number of unique core file versions that a program can create on a specific host system by setting the
system configuration variable enhanced-core-max-versions to the desired value: proc:
enhanced-core-name = 1
enhanced-core-max-versions = 8 The miminum value is 1, the maximum is 99,999, and the default is 16.
EXAMPLE
The following example shows a code fragment that calls the uswitch system call with the USW_CORE flag set: #include <signal.h> #include
<sys/uswitch.h>
/*
* Request enhanced core file naming for
* this process then create a core file.
*/ main() {
long uval = uswitch(USC_GET, 0);
uval = uswitch(USC_SET, uval | USW_CORE);
if (uval < 0) {
perror("uswitch");
exit(1);
}
raise(SIGQUIT); }
In general, the debugger dbx(1) is sufficient to deal with core images.
RELATED INFORMATION
sigaction(2), uswitch(2), sysconfigdb(8), dbx(1) delim off
core(4)