Hi Mahmmod,

When you want to compile a different level of debugging, you don't need a space between the target and the debugging level.

For example, the command might be:

make Common-vverb

instead of

make Common -VVerb


Also, it's important to note that the compile-time debug-level only controls which debug messages are compiled into the code, it doesn't control which of those messages are displayed at run-time.

By default, flexus displays messages with severity "Dev" or higher during run-time, regardless of what the compile-time debug level was set to. If you want to change the debug level, you need to use the following command at the simics prompt:

flexus.debug-set-severity "Iface"

If you want to turn on debugging when running create-initial-flexpoint or create-flexpoints, you can add the above command to either ./config/initial/start.simics or ./config/flexpoint/start.simics



Jason




On 10-05-07 9:50 AM, Mahmood Naderan wrote:
Hi,
When I set the debug level to "Iface" for <Common> there is no problem but for others like VVerb, Crit and ... I get errors that the first charachter is an invalid option. For example:

mahm...@localhost:flexus-3.0.0$ make Common -VVerb
make: invalid option -- 'V'
make: invalid option -- 'V'
Usage: make [options] [target] ...
Options:
    .......
    .......
This program built for i486-pc-linux-gnu
Report bugs to <[email protected]>
Also when I enable a debug level, at which stage of the simulation I can see the messages? ./create-initial-flexpoint or ./create-flexpoints or timing simulation?
*// Naderan *Mahmood;*


Reply via email to