Date: Tue, 10 Mar 2009 19:02:16 -0700 (PDT) From: Nate Eldredge <neldredge@math.ucsd.edu> To: vasanth raonaik <vasanth.raonaik@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Debugging init process. Message-ID: <Pine.GSO.4.64.0903101900160.3173@zeno.ucsd.edu> In-Reply-To: <d9f479c10903100953w4c600775oc06b997b67c472d6@mail.gmail.com> References: <d9f479c10903100953w4c600775oc06b997b67c472d6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Nate Eldredge neldredge@math.ucsd.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0903101900160.3173>