Log Message:
Sync with src/sys/arch/shark/conf/Makefile.shark.inc rev 1.14:
also need to strip out GCC 4.5's new .debug_pubtypes section.
while here, minor cleanup.
XXX: probably we should have something like ${ARM_AOUT_REMOVE_SECTIONS}
XXX: in bsd.own.mk
thanks for that. your
Manuel Bouyer bou...@netbsd.org wrote:
Module Name: src
Committed By: bouyer
Date: Sun Jul 3 10:40:16 UTC 2011
Modified Files:
src/sys/arch/amd64/conf: GENERIC
src/sys/arch/i386/conf: GENERIC
Log Message:
Add back DIAGNOSTIC option to x86 GENERIC kernels, as
On Sun, Jul 03, 2011 at 03:57:25PM +0100, Mindaugas Rasiukevicius wrote:
Thanks for enabling this, however you have ignored points raised on
tech-kern@. In such case, at least DEBUG
DEBUG is not as usefull as DIAGNOSTIC, and is very verbose.
My main point is to get KASSERT() back again.
DEBUG
Manuel Bouyer bou...@antioche.eu.org wrote:
On Sun, Jul 03, 2011 at 03:57:25PM +0100, Mindaugas Rasiukevicius wrote:
Thanks for enabling this, however you have ignored points raised on
tech-kern@. In such case, at least DEBUG
DEBUG is not as usefull as DIAGNOSTIC, and is very verbose.
My
On Sun, Jul 03, 2011 at 06:09:10PM +0100, Mindaugas Rasiukevicius wrote:
I also don't think we did reach a consensus about this either.
Well, I object on adding only DIAGNOSTIC, without DEBUG and DDB trace
enabled, as it is counter productive to the idea to gather more info.
I can't see how
Manuel Bouyer bou...@antioche.eu.org wrote:
On Sun, Jul 03, 2011 at 06:09:10PM +0100, Mindaugas Rasiukevicius wrote:
I also don't think we did reach a consensus about this either.
Well, I object on adding only DIAGNOSTIC, without DEBUG and DDB trace
enabled, as it is counter productive
On Sun, Jul 03, 2011 at 06:49:11PM +0100, Mindaugas Rasiukevicius wrote:
Manuel Bouyer bou...@antioche.eu.org wrote:
On Sun, Jul 03, 2011 at 06:09:10PM +0100, Mindaugas Rasiukevicius wrote:
I also don't think we did reach a consensus about this either.
Well, I object on adding only
On Sun, Jul 03, 2011 at 08:00:30PM +0200, Manuel Bouyer wrote:
Crash reports without backtrace - that is very often useless, and we do
A panic message (especually from KASSERT which gives the exact place)
is more usefull than the tail of a backtrace.
Xen has trace enabled by default, and
On Sun, Jul 03, 2011 at 08:22:51PM +, Jukka Ruohonen wrote:
Modified Files:
src/tests/syscall: t_mknod.c
Log Message:
Remove wrong check.
XXX: Why does this fail on tmpfs but not ffs?
That *should* fail. Probably ffs is failing to check.
--
David A. Holland
On Sun, Jul 03, 2011 at 11:45:24PM +, David Holland wrote:
On Sun, Jul 03, 2011 at 08:22:51PM +, Jukka Ruohonen wrote:
Modified Files:
src/tests/syscall: t_mknod.c
Log Message:
Remove wrong check.
XXX: Why does this fail on tmpfs but not ffs?
That *should*
10 matches
Mail list logo
