[gPXE-devel] [PATCH] [rom-o-matic] Add options to enable debug

Stefan Hajnoczi stefanha at gmail.com
Tue Jun 22 10:52:29 EDT 2010


On Tue, Jun 22, 2010 at 3:36 PM, Hogben, Colin H
<Colin.Hogben at ccfe.ac.uk> wrote:
> From 85b07af3ccbd563d9c7f42f91b65f87ca5ed5b18 Mon Sep 17 00:00:00 2001
> From: Colin Hogben <colin at pythontech.co.uk>
> Date: Thu, 18 Mar 2010 13:33:50 +0000
> Subject: [PATCH] [rom-o-matic] Add options to enable debug
>
> Add options to enable debug output in a subset of modules.
> Also fix typo which caused stderr to be lost if compilation failed.

Enabling DEBUG= in rom-o-matic is a great idea.  People often want to
see the debug output but prefer not to build from source.

I think we should drop the limited set of pre-defined DEBUG= options
and allow the raw DEBUG= list to be specified.  This gives access to
every debuggable object file and the debug level can be set too (e.g.
scsi:3 enables DBG + DBG2).

The syntax for DEBUG= is:
obj_1[:lvl][,obj_2[:lvl]]*

The object file name should be letters, digits, underscore, and
hyphen.  The debug level is an integer.  There may be one or more
object files listed, separated by a comma.

Stefan


More information about the gPXE-devel mailing list