[mvapich-discuss] Printing DEBUG_PRINT mesges

[Pavel Shamis (Pasha)]

You may to try to use V_PRINT macro (located in 
mpid/ch_gen2/ibverbs_header.h)
it is disabled by default but if you will rebuild the code with 
"-DVIADEV_DEBUG" flag it will enable the macro and will create the debug 
build - as result the performance
will be very bad.

In the code when you call the macro you may setup on witch "debug level" 
you want to print the message: DEBUG00 - DEBUG03

For setting specific debug level during run you may use 
VIADEV_DEBUG_LEVEL parameter.
For example  - VIADEV_DEBUG_LEVEL=1 will say to mvapich to run in level 
1 of debug.

But As Matt say before all this stuff we use for internal development 
and you should understand very well what are you doing.

Pasha.


Matthew Koop wrote:
> Nilesh,
>
> DEBUG_PRINT is used for internal development, so we cannot guarantee that
> the messages printed will be useful to others (or correct). As such, we do
> not support this option for the end-user.
>
> Is there a particular problem you are experiencing that we can address?
>
> Matt
>
>
> On Mon, 3 Sep 2007, Nilesh Awate wrote:
>
>   
>> Hi All,
>>
>> I'm using mvapich2-1.0-beta with ofed1.2 udapl interface.
>>
>> I want to print DEBUG_PRINT masseges for that i've included DDEBUG flag in
>> make.mvapich.udapl make file
>>
>> but while making its give error in that perticular DEBUG_PRINT statements
>> "variables not defined"
>>
>> is there anything else  setting of flags ...
>>
>> waiting for reply
>>
>> Nilesh,
>> C-DAC, India
>>
>>
>> _______________________________________________
>> mvapich-discuss mailing list
>> mvapich-discuss at cse.ohio-state.edu
>> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>
>>     
>
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>
>