public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3932] New: fcatch may not exit on some programs
Date: Mon, 29 Jan 2007 18:10:00 -0000	[thread overview]
Message-ID: <20070129181037.3932.pmuldoon@redhat.com> (raw)

[pmuldoon@localhost bindir]$ gcc -g  ~/segfault.c -o ~/segfault -lpthread
[pmuldoon@localhost bindir]$ fcatch ~/segfault
Print Entry Thread 1
 
Print Entry Thread 2
 
SIGSEGV detected: dumping stack trace
#0 0x804851f in main () from: /home/pmuldoon/segfault.c#36
#1 0x4da7ff2c in __libc_start_main ()
#2 0x8048411 in _start ()

fcatch does not exit, but seems to sit waiting hanging at the console.

System is Fedora Core 6

[pmuldoon@localhost frysk_bin]$ uname -a
Linux localhost.localdomain 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST
2007 i686 i686 i386 GNU/Linux

-- 
           Summary: fcatch may not exit on some programs
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: pmuldoon at redhat dot com


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

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


             reply	other threads:[~2007-01-29 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 18:10 pmuldoon at redhat dot com [this message]
2007-01-29 18:11 ` [Bug general/3932] " pmuldoon at redhat dot com
2007-02-23 15:09 ` mcvet 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=20070129181037.3932.pmuldoon@redhat.com \
    --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).