[Paraview] [Paraview-developers] Paraview with python problem

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Wed Dec 18 11:06:27 EST 2013


Gerald,

The change you did, is invalid, since pcTest ends up being pointing to
a dangling pointer. It works in it's original form since the temporary
object returned by toAscii() is not deleted until the call returns.
More and more, I think it's definitely a build/dependency issue. I'd
suggest doing  a clean build, if you haven't already. Delete
everything in the build directory (or start with a new one) and start
afresh before debugging further.

Utkarsh


On Wed, Dec 18, 2013 at 10:13 AM, Lodron, Gerald
<Gerald.Lodron at joanneum.at> wrote:
>
> It closes in
>
> pxm->RegisterProxy("representations", pcTest, reprProxy);
>
> at pqObjectBuilder.cxx at line 527, and when I set a breakpoint into registerProxy of vtkSMProxyManager it gets never hit. It seems that the name.toAscii().data() is corrupted, but name is a vaild string "DataRepresentation1". When I write
>
> const char* pcTest = name.toAscii().data();
>   //pxm->RegisterProxy("representations", name.toAscii().data(), reprProxy);
>   pxm->RegisterProxy("representations", pcTest, reprProxy);
>
> and watch at pcTest it is " îþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþîþÓ6
>
> ¡~ hêè Xlø " so it seems that:
>
> Name.toAscii().data() is not allowed in that combination
> OR
> The memory is completely corrupted from somewhere else......
>
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Gesendet: Mittwoch, 18. Dezember 2013 15:52
> An: Lodron, Gerald
> Cc: Paraview Developer (Paraview-developers at paraview.org); Paraview User (paraview at paraview.org)
> Betreff: Re: [Paraview-developers] Paraview with python problem
>
> Weird. Let's try this, but a break point in that method. It'll only be called once after you hit "apply". Then step into the code, including createDataRepresentation(..). If you cannot step, I think it's a problem with mismatched/improperly built libraries or something. If the call stack starts making no sense, it's definitely that, and I'd recommend a clean build -- start with an empty binary directory.
>
> Utkarsh
>
> On Wed, Dec 18, 2013 at 9:45 AM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
>> Hi,
>>
>> I am currently debugging, it closes (not crashing!) in
>>
>> pqDataRepresentation* pqDisplayPolicy::newRepresentation(pqOutputPort* port,
>>   pqView* view) const
>> {
>>   return pqApplicationCore::instance()->getObjectBuilder()->
>>     createDataRepresentation(port, view); } Of pqDisplayPolicy.cxx
>>
>> Here i cannot debug in for any reason (i come somewhere into assembler of qt and when I step out it closes). I will try debugging more ...
>> PS: I also checked the successful RequestData return of the sources so the source is correctly applied, it closes afterwards...
>>
>> Gerald
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Gesendet: Mittwoch, 18. Dezember 2013 15:40
>> An: Lodron, Gerald
>> Cc: Paraview User (paraview at paraview.org); Paraview Developer
>> (Paraview-developers at paraview.org)
>> Betreff: Re: [Paraview-developers] Paraview with python problem
>>
>> Gerald,
>>
>> Since you compiled from source, can you do debug build and then run through a debugger to see why it's aborting? I don't think I've seen this behaviour before. I wonder if its related to the dependency issue. Was this a clean build or were you doing an incremental build?
>>
>> Utkarsh
>>
>> On Wed, Dec 18, 2013 at 9:19 AM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
>>> Hi
>>>
>>>
>>>
>>> I successfully compiled paraview 4.1.0 with python 2.7.3 enabled in 32 bit.
>>> Paraview also starts but when I generate ANY data (over open file or
>>> over
>>> sources->Sphere or box or anything else etc.) it closes after
>>> sources->pressing
>>> Apply. Does anyone has a clue what could cause that strange behaviour?
>>>
>>>
>>>
>>> Thanks for advice...
>>>
>>>
>>>
>>> Best regards
>>>
>>> Gerald Lodron
>>>
>>>
>>>
>>> _________________________________________________________________
>>>
>>>
>>>
>>> JOANNEUM RESEARCH Forschungsgesellschaft mbH
>>>
>>>
>>>
>>> DIGITAL - Institute for Information and Communication Technologies
>>>
>>> Steyrergasse 17, 8010 Graz, Austria
>>>
>>>
>>>
>>> phone: +43 316 876-1751
>>>
>>> fax: +43 316 8769-1751
>>>
>>> e-mail: gerald.lodron at joanneum.at
>>>
>>> web: www.joanneum.at/digital
>>>
>>> _________________________________________________________________
>>>
>>>
>>>
>>> This message and any attached files are confidential and intended
>>> solely for the addressee(s). Any publication, transmission or other
>>> use of the information by a person or entity other than the intended
>>> addressee(s) is prohibited. If you receive this in error please
>>> contact the sender and delete the material. The sender does not
>>> accept liability for any errors or omissions as a result of the transmission.
>>>
>>>
>>>
>>> Please consider the environment before printing this page.
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>


More information about the ParaView mailing list