10 More Discussions You Might Find Interesting
1. Programming
Hey everyone,
I'm trying to attach to a process that is crashing so I can debug the source code. I've tried this:
dbx -a PID
stop at "file.cpp":line#
However, nothing ever breaks. The service crashes and restarts, but I never see it hitting the code. I've tried to use a core file, but... (2 Replies)
Discussion started by: ctote
2 Replies
2. Programming
I have tried lots of stuff but i can't get it working, i have also found a Thread in this Forum about it but it didn't describe how the program has to be run ect.
My issue is that i want to run a program with multiple arguments eg.
./myprog arg1 arg2 arg3 arg4 arg5
with dbx, but i cant get... (8 Replies)
Discussion started by: alcatros
8 Replies
3. AIX
Hi,
We are porting a virtual machine application which emits native PowerPC instructions. The instructions are written to the data segment and are then executed, similar to the JIT / hot spot technology used in the Java VM.
The problem is that the AIX debugger (dbx) will not show me stack... (3 Replies)
Discussion started by: nrgiii
3 Replies
4. Programming
hi i have executable(eg test) of my application
that has the following syntax to run
test -Ddatabase_name Inputfile
Now i want to debug it using dbx
so i do
dbx test
(dbx) stop at /abc/test/test.c:90
stop at /abc/test/test.c:90
^ syntax error
the... (0 Replies)
Discussion started by: mad_man12
0 Replies
5. UNIX for Advanced & Expert Users
Hi ..
I have a core_dump in the server... AIX 5.3 . It was created by on proc executable called "ProcessIse" . from the log report i found the source file name
"ProcessIseInterface.C" which created the core file.
the core file name is : "core" under /iprs/bin directory.
can you help me... (1 Reply)
Discussion started by: vparunkumar
1 Replies
6. AIX
Hi ..
I have a core_dump in the server... AIX 5.3 . It was created by on proc executable called "ProcessIse" . from the log report i found the source file name
"ProcessIseInterface.C" which created the core file.
the core file name is : "core" under /iprs/bin directory.
can you help me... (1 Reply)
Discussion started by: vparunkumar
1 Replies
7. Programming
I have a problem whith dbx: there is no dbx installed!!!
Could someone tell me where do i get dbx program and how to install it?
Thanks. (1 Reply)
Discussion started by: calloc
1 Replies
8. Solaris
Hi All,
I've been using Linux for past 2yrs for professional dev.
Im well-off with gnu gdb.
I am a C++ developer.
Now that i use solaris, I need help on DBX.
Regards,
Sumanth (1 Reply)
Discussion started by: Sumanth
1 Replies
9. Programming
I am trying to debug a program, which had generated a core dump. When I issue 'where' command, it list me filename along with line number, which in case is not at all there in the .c file.
Example:
(dbx) where
func1(var1= (...), var2 = 86, var3 = 0,var4 = 0)
, line 87 in "prog.f"
main(),... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
10. Programming
Which is better??
I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it???
:cool: (1 Reply)
Discussion started by: jyotipg
1 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)