public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "walters at verbum dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5921] New: fcatch should trace interpreted executables too
Date: Wed, 12 Mar 2008 15:36:00 -0000	[thread overview]
Message-ID: <20080312153546.5921.walters@verbum.org> (raw)

It'd be nice if fcatch was usable on non-ELF files.  For example, I'd like to
have a Python script:

#!/usr/bin/python
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
/usr/lib64/libpython2.5.so.1.0
#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

-- 
           Summary: fcatch should trace interpreted executables too
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: walters at verbum dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=5921

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2008-03-12 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 15:36 walters at verbum dot org [this message]
2008-03-12 19:32 ` [Bug general/5921] " cagney at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080312153546.5921.walters@verbum.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).