Date: Wed, 11 Mar 2009 08:51:38 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Nate Eldredge <neldredge@math.ucsd.edu> Cc: freebsd-hackers@freebsd.org, vasanth raonaik <vasanth.raonaik@gmail.com> Subject: Re: Debugging init process. Message-ID: <20090311085138.23982deb8g8234w0@webmail.leidinger.net> In-Reply-To: <Pine.GSO.4.64.0903101900160.3173@zeno.ucsd.edu> References: <d9f479c10903100953w4c600775oc06b997b67c472d6@mail.gmail.com> <Pine.GSO.4.64.0903101900160.3173@zeno.ucsd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 it >> throws > > As others mentioned, this is explicitly disabled. You 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? It's a fairly > simple 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 option (I don't know if it special-cases init or not). Bye, Alexander. -- Don't interfere with the stranger's style. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090311085138.23982deb8g8234w0>