Red Hat Bugzilla – Bug 103219
pstack segfaults when reading C++ executables.
Last modified: 2007-03-27 00:09:19 EDT
Description of problem:
When running pstack against executables that were generated from c++ code,
pstack segfaults. Unfortunately, it does not leave a core file around.
Version-Release number of selected component (if applicable):
All the time.
Steps to Reproduce:
1. Create the following C++ file, and call it test.c
int main(int argc, char* argv)
std::cout << "Hello world, press enter to continue..." << std::endl;
2. Compile this with g++.
3. Run the program.
4. Run pstack against the running program.
[root@nsdlinux06 root]# pstack 23447
pstack signal received: Segmentation fault
A stack trace (-:
As I mentioned above it does not produce a core file (and yes I am using
ulimit -c before hand), so I can't really figure out where its dying
easily. Also, it fails against other C++ programs, this was just the distilled
down test case.
It appears that the rpm for 1.1-1.1 doesn't upgrade correctly.
IE: rpm -U appears to only update the rpm db. rpm -q reports pstack 1.1-1.1,
but rpm -q --changelog displays the old changelog.
rpm -e pstack; rpm -i pstack-1.1-1.1 corrects the issue.
This bug was already reported separately and has been fixed.
New packages will be available in rawhide before too long, and that
can be rebuilt on RHL9.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.