public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5927] New: fhpd `Unhandled real stop event for task' for GDB
Date: Thu, 13 Mar 2008 08:44:00 -0000	[thread overview]
Message-ID: <20080313084358.5927.jan.kratochvil@redhat.com> (raw)

Trying to run fhpd to debug GDB crashes fhpd:

cat >cmd <<EOH
shell echo 'int main (void) { return 0; }' >/tmp/main.c
shell gcc -o /tmp/main /tmp/main.c -Wall -ggdb2
file /tmp/main
run
quit
EOH

fhpd -- `which gdb` -silent -x ./cmd
Loaded executable file: /usr/bin/gdb
(fhpd) run
Attached to process 28827
starting/running with this command: /usr/bin/gdb -silent -x ./cmd2 
Running process 28827
(fhpd) Using host libthread_db library "/lib64/libthread_db.so.1".
Unhandled real stop event for task:
{frysk.proc.live.LinuxPtraceTask@2fa7b255,pid=28835,tid=28835,state=running}
$PWD/cmd2:4: Error in sourced command file:
linux_test_for_tracefork: waitpid: unexpected status 0.
(gdb) 

frysk-0.0.1.2008.02.29.rh1-1.fc8.x86_64
kernel-2.6.24.3-12.fc8.x86_64

-- 
           Summary: fhpd `Unhandled real stop event for task' for GDB
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: jan dot kratochvil at redhat dot com


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

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


                 reply	other threads:[~2008-03-13  8:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080313084358.5927.jan.kratochvil@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).