[Paraview-developers] How to activate (selectively if possible ?) debug traces when using ParaView ?

[houssen]

OK, I'll do that !

Thanks,

Franck

Le 2016-04-06 1:48, Utkarsh Ayachit a écrit :
> In practise, I have never found the debug message printed by setting
> SetDebug(1) on any vtkObject useful.
>
> Instead, I'd suggest just using a debugger, even if that means
> rebuilding as "Debug". Especially if it's a segfault, the call stack
> for the segfault is generally useful in spotting the issue. You can
> also try passing "--enable-bt" as a command line argument to dump out
> the call stack on segfault to the output terminal.
>
> On Tue, Apr 5, 2016 at 11:06 AM, houssen <houssen at ipgp.fr> wrote:
>> How to activate (selectively if possible ?) debug traces when using 
>> ParaView
>> ?
>>
>> I am in the process of creating new couples of HDF5 / XDMF files : 
>> for now,
>> it is bugged, so the XDMF reader crashes when I open it in ParaView. 
>> I need
>> to "see" why ParaView crashes : that is, I need to understand "where 
>> and/or
>> why" my HDF5 / XDMF are bugged (and trigger later on a crash in 
>> ParaView).
>> Ideally, I would need to activate only debug traces for xdmf reader.
>>
>> First, I tried to find (Google search) if a variabe like 
>> PARAVIEW_DEBUG
>> could be set before running ParaView but it seems no such variable 
>> exists
>> (this->DebugOn() only helps if you have a problem in one of your own 
>> filter
>> - this is not the case here). Then, I looked in the GUI (menu, 
>> options,
>> settings) but I didn't find any way to turn on traces. I also tried 
>> to get
>> info from gdb but I get a low level of informations (stack and some 
>> relevant
>> infos but no messages on problems before crashing) as my ParaView is 
>> built
>> from source in RelWithDebInfo mode (I'd like to avoid to recompile 
>> in debug
>> : it would take hours...). I looked around
>> 
>> ParaView-v5.0.0-source/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfObject.h 
>> and
>> 
>> ParaView-v5.0.0-source/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfObject.cxx
>> (XdmfObject::GetGlobalDebug) but it doesn't help really at first 
>> glance :
>> GetGlobalDebug is not implemented like I would have imagined (thats 
>> is in a
>> getenv("PARAVIEW_DEBUG")-like way).
>>
>> More generally, is it possible to activate debug / warning / info 
>> traces
>> according to "what I would like to do" ? (for instance, activating 
>> only
>> shrink filter traces but not xdmf reader traces, or the opposite ?) 
>> This
>> would help understanding / locating problems when they occur. It 
>> would be a
>> convenient feature.
>>
>> FH
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers