Date: Wed, 11 Mar 2009 15:54:44 +0100 From: =?ISO-8859-1?Q?Marius_N=FCnnerich?= <marius@nuenneri.ch> To: Alexander Leidinger <Alexander@leidinger.net> Cc: Nate Eldredge <neldredge@math.ucsd.edu>, freebsd-hackers@freebsd.org, vasanth raonaik <vasanth.raonaik@gmail.com> Subject: Re: Debugging init process. Message-ID: <b649e5e0903110754k59ff61e8u2f41b88cee475949@mail.gmail.com> In-Reply-To: <20090311085138.23982deb8g8234w0@webmail.leidinger.net> References: <d9f479c10903100953w4c600775oc06b997b67c472d6@mail.gmail.com> <Pine.GSO.4.64.0903101900160.3173@zeno.ucsd.edu> <20090311085138.23982deb8g8234w0@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 11, 2009 at 08:51, Alexander Leidinger <Alexander@leidinger.net> wrote: > Quoting Nate Eldredge <neldredge@math.ucsd.edu> (from Tue, 10 Mar 2009 > 19:02:16 -0700 (PDT)): > >> On Tue, 10 Mar 2009, vasanth raonaik wrote: >> >>> Hello Team, >>> >>> I need to debug init process. I am not able to attach init to gdb and i= t >>> throws >> >> As others mentioned, this is explicitly disabled. =A0You could re-enable= it >> by hacking the kernel, but it could cause other unexpected problems. >> >> Alternatively, there's always "printf debugging". >> >> What is wrong with init, that you need to debug it? =A0It's a fairly sim= ple >> program that's been around for a long time and should be pretty stable. > > If this is on -current and depending on the problem, dtrace may be an opt= ion > (I don't know if it special-cases init or not). > DTrace is not available for userland processes yet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b649e5e0903110754k59ff61e8u2f41b88cee475949>