Bug 5921 - fcatch should trace interpreted executables too
Summary: fcatch should trace interpreted executables too
Status: RESOLVED DUPLICATE of bug 5878
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 5878
  Show dependency treegraph
Reported: 2008-03-12 15:35 UTC by Colin
Modified: 2008-03-12 19:31 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Colin 2008-03-12 15:35:46 UTC
It'd be nice if fcatch was usable on non-ELF files.  For example, I'd like to
have a Python script:

import os,signal
os.kill(os.getpid(), signal.SIGSEGV)

Saving that as say ~/bin/segfault, I'd like to be able to do:

fcatch ~/bin/segfault

Current output is:
Error: invalid `Elf' handle

Expected output:

fcatch: from PID 2620 TID 2620:
SIGSEGV(11) detected - dumping stack trace for TID 2620
#0 0x00000034cbc31357 in __GI___kill () from /lib64/libc-2.7.so
#1 0x0000003b49ae176d in posix_kill () from /usr/lib64/libpython2.5.so.1.0
#2 0x0000003b49ab5b79 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.5.so.1.0
#3 0x0000003b49ab6862 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.5.so.1.0
#4 0x0000003b49ab68a2 in PyEval_EvalCode () from /usr/lib64/libpython2.5.so.1.0
#5 0x0000003b49ad08b2 in run_mod () from /usr/lib64/libpython2.5.so.1.0
#6 0x0000003b49ad0986 in PyRun_FileExFlags () from /usr/lib64/libpython2.5.so.1.0
#7 0x0000003b49ad1e78 in PyRun_SimpleFileExFlags () from
#8 0x0000003b49adb21e in Py_Main () from /usr/lib64/libpython2.5.so.1.0
#9 0x00000034cbc1e074 in __libc_start_main () from /lib64/libc-2.7.so
#10 0x0000000000400649 in _start () from /usr/bin/python
Comment 1 Andrew Cagney 2008-03-12 19:31:23 UTC
Duping to 5878; once:
  fexe script
works, this will two.

*** This bug has been marked as a duplicate of 5878 ***