Date: Sun, 1 Oct 2000 16:17:01 -0400 (EDT) From: rwatson@freebsd.org To: FreeBSD-gnats-submit@freebsd.org Subject: gnu/21685: remote gdb: ptrace(PT_GETDBREGS) failed: No such process Message-ID: <200010012017.QAA57771@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
>Number: 21685
>Category: gnu
>Synopsis: remote gdb: ptrace(PT_GETDBREGS) failed: No such process
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Oct 01 13:20:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Robert Watson
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
FreeBSD alsvid.watson.org 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Sep 22 10:54:51 EDT 2000 robert@alsvid.watson.org:/data/fbsd-current/fresh/acl/src/sys/compile/ACL i386
Using gdb to remote debug a kernel.
>Description:
Gdb spits out lots of ptrace() errors during remote debugging, whereas
previously it did not. Since ptrace() should only be used for local
debugging, there's probably a call to ptrace() that should not be occuring.
Don't have the threshold date that it started due to spotty following of
-CURRENT.
>How-To-Repeat:
(kgdb) target remote /dev/cuaa0
Remote debugging using /dev/cuaa0
ptrace(PT_GETDBREGS) failed: No such process
Debugger (msg=0xc039af4f "Boot flags requested debugger")
at ../../i386/i386/db_interface.c:326
326 in_Debugger = 0;
>Fix:
Not included. This doesn't appear to result in actual breakage, just an
annoying message getting printed fairly frequently.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010012017.QAA57771>