04-09-2004
Please follow the link:
DBX UNABLE TO TRACE FAULTING THREAD STACK IN TRUNCATED CORE
Since I cannot implement the fix and try it out, but I have a general question. Even after the fix do I need to have SA_FULLDUMP flag set OR even with SA_PARTDUMP I will be able to read data from core file to which I am currently receiving the following error:
"warning: Unable to access address 0x200009cc from core"
Thanks in advance.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. Programming
Hi,
We are trying to run dbx on a core file for which we have the original executable and libs, but not the source / object tree. We have recompiled the objects from the original source, but dbx complains that they were compiled at a different time, and refuses to read them:
Object file:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies
4. 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
5. 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
6. 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
7. AIX
Background
-------------
Os: IBM AIXL 5.1 (Unix)
Problem
-------------
I run the dbx in csh as follows
% dbx mainprog
-- The following is the systemm replay
Type 'help' for help.
reading symbolic information ...warning: stab entry unrecognized: name ,type 45, class a8, value 0'
... (1 Reply)
Discussion started by: skfn1203
1 Replies
8. 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
9. Shell Programming and Scripting
Hi,
I ahd created my executable file from makefile on AIX.
Now I want to debug my code using dbx.
I typed:
dbx help
It goes into (dbx) prompt
But afte that i do not know what to do to put breakpoints in my program and how to run step by step.
Help me out ASAP.
Thanks in... (0 Replies)
Discussion started by: Poonamol
0 Replies
10. 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
LEARN ABOUT REDHAT
file::stat
File::stat(3pm) Perl Programmers Reference Guide File::stat(3pm)
NAME
File::stat - by-name interface to Perl's built-in stat() functions
SYNOPSIS
use File::stat;
$st = stat($file) or die "No $file: $!";
if ( ($st->mode & 0111) && $st->nlink > 1) ) {
print "$file is executable with lotsa links
";
}
use File::stat qw(:FIELDS);
stat($file) or die "No $file: $!";
if ( ($st_mode & 0111) && $st_nlink > 1) ) {
print "$file is executable with lotsa links
";
}
DESCRIPTION
This module's default exports override the core stat() and lstat() functions, replacing them with versions that return "File::stat"
objects. This object has methods that return the similarly named structure field name from the stat(2) function; namely, dev, ino, mode,
nlink, uid, gid, rdev, size, atime, mtime, ctime, blksize, and blocks.
You may also import all the structure fields directly into your namespace as regular variables using the :FIELDS import tag. (Note that
this still overrides your stat() and lstat() functions.) Access these fields as variables named with a preceding "st_" in front their
method names. Thus, "$stat_obj->dev()" corresponds to $st_dev if you import the fields.
To access this functionality without the core overrides, pass the "use" an empty import list, and then access function functions with their
full qualified names. On the other hand, the built-ins are still available via the "CORE::" pseudo-package.
BUGS
As of Perl 5.8.0 after using this module you cannot use the implicit $_ or the special filehandle "_" with stat() or lstat(), trying to do
so leads into strange errors. The workaround is for $_ to be explicit
my $stat_obj = stat $_;
and for "_" to explicitly populate the object using the unexported and undocumented populate() function with CORE::stat():
my $stat_obj = File::stat::populate(CORE::stat(_));
NOTE
While this class is currently implemented using the Class::Struct module to build a struct-like class, you shouldn't rely upon this.
AUTHOR
Tom Christiansen
perl v5.8.0 2002-06-01 File::stat(3pm)