Robert Watson wrote:
On Mon, 14 Nov 2005, Simon Ironside wrote:
/sys/i386/conf/GENERIC has this line uncommented - is this on purpose?
I commented it out before building a new kernel.
makeoptions DEBUG=-g
This was by accident, but actually isn't a bad idea. We discovered the
problem at
On Mon, 14 Nov 2005, Simon Ironside wrote:
/sys/i386/conf/GENERIC has this line uncommented - is this on purpose? I
commented it out before building a new kernel.
makeoptions DEBUG=-g
This was by accident, but actually isn't a bad idea. We discovered the
problem at the last minute, after
safe to leave un-commented no hindrance in performance.
On Mon, 2005-11-14 at 08:53 +, Simon Ironside wrote:
> Hello,
>
> > I think this is intentional. Having DEBUG=-g means that you have a
> > kernel.debug which contains debugging symbols, which is quite useful
> > if you get a kernel pani
On 11/14/05, Simon Ironside <[EMAIL PROTECTED]> wrote:
[snip]
> This has changed since 5.4 - I just wondered why and whether I would be
> best leaving it as is or commenting it out.
My personal suggestion would be that you keep it as-is, since it saves
your time when you have kernel panics and wan
Hello,
I think this is intentional. Having DEBUG=-g means that you have a
kernel.debug which contains debugging symbols, which is quite useful
if you get a kernel panic and want to report it back. On the other
hand, debugging symbols would be stripped before you install a new
kernel so it does
Hi, Simon,
On 11/14/05, Simon Ironside <[EMAIL PROTECTED]> wrote:
> Hi,
>
> /sys/i386/conf/GENERIC has this line uncommented - is this on purpose? I
> commented it out before building a new kernel.
>
> makeoptions DEBUG=-g
I think this is intentional. Having DEBUG=-g means that you have a
ke
Hi,
/sys/i386/conf/GENERIC has this line uncommented - is this on purpose? I
commented it out before building a new kernel.
makeoptions DEBUG=-g
Cheers,
Simon
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
