From: Allen Hopkins <allenh@eecs.berkeley.edu>
To: Mike Chrabaszcz <mikec@mediabolic.com>
Cc: gdb@sources.redhat.com, Brad A Krebs <brad@eecs.berkeley.edu>
Subject: Re: gdb 6.3 giving a "Child process unexpectedly missing" error
Date: Fri, 07 Jan 2005 18:42:00 -0000 [thread overview]
Message-ID: <41DED7FD.1010602@eecs.berkeley.edu> (raw)
In-Reply-To: <A6B3D2F0FED7564699FFE261012FF2AB119F6A@samson.internal.mediabolic.com>
I can only say that I'm in the same boat, and also mystified.
The error is the same:
> Program terminated with signal ?, Unknown signal.
> The program no longer exists.
> You can't do that without a process to debug.
Linux was just updated on my machine. "uname -a" says this:
> Linux hig.eecs.berkeley.edu 2.6.9-1.11_FC2smp #1 SMP Sun Jan 2 16:19:13 EST 2005 i686 i686 i386 GNU/Linux
-Allen Hopkins
UCBerkeley ERL
Mike Chrabaszcz wrote:
> I am running Fedora Core3 and have recently updated. And now, I can no longer gdb run on any program. Any suggestions?
>
> Regards,
> MikeC.
>
> ----------------------------------------------------
> gdb ./test
>
> GNU gdb 6.3
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
>
> (gdb) r
> Starting program: /test
> warning: Child process unexpectedly missing: No child processes
>
> Program terminated with signal ?, Unknown signal.
> The program no longer exists.
> You can't do that without a process to debug.
> (gdb)
>
next prev parent reply other threads:[~2005-01-07 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 18:21 Mike Chrabaszcz
2005-01-07 18:24 ` Kris Warkentin
2005-01-07 18:42 ` Allen Hopkins [this message]
2005-01-08 3:18 ` Andrew Cagney
2005-01-07 18:31 Mike Chrabaszcz
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=41DED7FD.1010602@eecs.berkeley.edu \
--to=allenh@eecs.berkeley.edu \
--cc=brad@eecs.berkeley.edu \
--cc=gdb@sources.redhat.com \
--cc=mikec@mediabolic.com \
/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