This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: process attaching gdb to itself

From: Andrew Cagney <ac131313 at redhat dot com>
To: Daniel Jacobowitz <drow at mvista dot com>
Cc: Michael Elizabeth Chastain <mec at shout dot net>,aurelien dot chanudet at enst dot fr, gdb at sources dot redhat dot com
Date: Mon, 29 Sep 2003 10:52:50 -0400
Subject: Re: process attaching gdb to itself
References: <200309282225.h8SMP9Rf026649@duracef.shout.net> <3F77622C.8090403@redhat.com> <20030928232401.GA20802@nevyn.them.org> <3F7831F3.6010203@redhat.com> <20030929132631.GA17873@nevyn.them.org>

I feel ill. What happens, for instance, if /proc isn't there?

At this point in its life, Linux can just assume the /proc filesystem
is available.  Linus has repeatedly refused to duplicate information
available via /proc through another interface.

Sounds like the GNU/Linux back end should, finally, switch to /proc?

Andrew

Follow-Ups:
- Re: process attaching gdb to itself
  - From: Daniel Jacobowitz

References:
- Re: process attaching gdb to itself
  - From: Michael Elizabeth Chastain
- Re: process attaching gdb to itself
  - From: Andrew Cagney
- Re: process attaching gdb to itself
  - From: Daniel Jacobowitz
- Re: process attaching gdb to itself
  - From: Andrew Cagney
- Re: process attaching gdb to itself
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]