Andi Kleen writes:
It's still useless - it is too bloated to turn on by default
and then if you need it you still won't have it. And when you
explicitely turn it on then you likely don't need it because
you control the source.
Hmm. Would a BUG_ON_WITH_TEXT be a better solution? The home-grown
On Mon, 27 June 2005 15:27:50 +0300, Pekka J Enberg wrote:
> On Mon, 27 Jun 2005, Andi Kleen wrote:
> > It won't work for me because it'll bloat the kernel .text
> > considerable. There is a reason why BUG is implemented
> > like it is. Compare it.
>
> The assertion codes bloat the kernel all the
On Mon, Jun 27, 2005 at 03:27:50PM +0300, Pekka J Enberg wrote:
> On Mon, 27 Jun 2005, Andi Kleen wrote:
> > It won't work for me because it'll bloat the kernel .text
> > considerable. There is a reason why BUG is implemented
> > like it is. Compare it.
>
> The assertion codes bloat the kernel all
l as well as the EIP and oops trace. This aids
debugging but costs about 70-100K of memory.
+config DEBUG_BUG_ON_VERBOSE
+ bool "Verbose BUG_ON() reporting"
+ depends on DEBUG_KERNEL && BUG
+ default false
+ help
+ Say Y here to make BUG_O
