[vtk-developers] VTK Coverage drop

Mathieu Westphal mathieu.westphal at kitware.com
Thu Dec 3 13:04:45 EST 2015


Thx, i can reproduce now

Mathieu Westphal

On Thu, Dec 3, 2015 at 6:48 PM, Bill Lorensen <bill.lorensen at gmail.com>
wrote:

> Module_vtkPythonInterpreter:BOOL=ON
>
>
> On Thu, Dec 3, 2015 at 12:44 PM, Mathieu Westphal
> <mathieu.westphal at kitware.com> wrote:
> > I see it fails on kargard, but cannot reproduce locally, i'm trying to
> work
> > with vncViewer on kargard but it is not easy.
> >
> > Can you precise me wich option you have activated in cmake ? python + tcl
> > does not seem enough for me.
> >
> > Mathieu
> >
> > Mathieu Westphal
> >
> > On Thu, Dec 3, 2015 at 6:11 PM, Mathieu Westphal
> > <mathieu.westphal at kitware.com> wrote:
> >>
> >> That's mine, i will look at it.
> >>
> >> Mathieu Westphal
> >>
> >> On Thu, Dec 3, 2015 at 6:04 PM, Ken Martin <ken.martin at kitware.com>
> wrote:
> >>>
> >>> Bad memory access in vtkPython.h below this->Force is true.  Not sure
> if
> >>> that rings a bell with anyone.  Build with Tcl and Python and the
> PyInterp
> >>> option to get the error
> >>>
> >>> class vtkPythonScopeGilEnsurer
> >>> {
> >>> public:
> >>>   vtkPythonScopeGilEnsurer(bool force = false)
> >>>     : State(PyGILState_UNLOCKED)
> >>>     {
> >>> #ifdef VTK_PYTHON_FULL_THREADSAFE
> >>>     // Force is always true with FULL_THREADSAFE
> >>>     force = true;
> >>> #endif
> >>>     this->Force = force;
> >>>     if (this->Force)
> >>>       {
> >>>       this->State = PyGILState_Ensure();
> >>>
> >>> stack is
> >>>
> >>> >
> >>> >
> vtkPythonInterpreter-6.3.dll!vtkPythonScopeGilEnsurer::vtkPythonScopeGilEnsurer(bool
> >>> > force)  Line 152 + 0x6 bytes C++
> >>>
> >>>
> vtkPythonInterpreter-6.3.dll!vtkPythonInteractiveInterpreter::vtkInternals::CleanupPythonObjects()
> >>> Line 48 + 0xc bytes C++
> >>>
> >>>
> vtkPythonInterpreter-6.3.dll!vtkPythonInteractiveInterpreter::vtkInternals::~vtkInternals()
> >>> Line 38 + 0xa bytes C++
> >>>
> >>>
> vtkPythonInterpreter-6.3.dll!vtkPythonInteractiveInterpreter::vtkInternals::`scalar
> >>> deleting destructor'()  + 0x2c bytes C++
> >>>
> >>>
> vtkPythonInterpreter-6.3.dll!vtkPythonInteractiveInterpreter::~vtkPythonInteractiveInterpreter()
> >>> Line 142 + 0x2f bytes C++
> >>>   vtkPythonInterpreter-6.3.dll!vtkPythonInteractiveInterpreter::`vector
> >>> deleting destructor'()  + 0x7d bytes C++
> >>>
>  vtkCommonCore-6.3.dll!vtkObjectBase::UnRegisterInternal(vtkObjectBase *
> >>> __formal, int check)  Line 232 + 0x31 bytes C++
> >>>   vtkCommonCore-6.3.dll!vtkObject::UnRegisterInternal(vtkObjectBase *
> o,
> >>> int check)  Line 901 C++
> >>>   vtkCommonCore-6.3.dll!vtkObjectBase::UnRegister(vtkObjectBase * o)
> >>> Line 190 C++
> >>>   vtkCommonCore-6.3.dll!vtkObjectBase::Delete()  Line 135 C++
> >>>   vtkCommonCoreTCL-6.3.dll!vtkObjectBaseCppCommand(vtkObjectBase * op,
> >>> Tcl_Interp * interp, int argc, char * * argv)  Line 109 C++
> >>>   vtkCommonCoreTCL-6.3.dll!vtkObjectCppCommand(vtkObject * op,
> Tcl_Interp
> >>> * interp, int argc, char * * argv)  Line 855 + 0x25 bytes C++
> >>>
> >>>
> vtkPythonInterpreterTCL-6.3.dll!vtkPythonInteractiveInterpreterCppCommand(vtkPythonInteractiveInterpreter
> >>> * op, Tcl_Interp * interp, int argc, char * * argv)  Line 342 + 0x25
> bytes
> >>> C++
> >>>
> >>>
> vtkPythonInterpreterTCL-6.3.dll!vtkPythonInteractiveInterpreterCommand(void
> >>> * cd, Tcl_Interp * interp, int argc, char * * argv)  Line 33 C++
> >>>   vtkCommonCoreTCL-6.3.dll!vtkTclGenericDeleteObject(void * cd)  Line
> 132
> >>> C++
> >>>
> >>>
> >>> On Thu, Dec 3, 2015 at 11:35 AM, Ken Martin <ken.martin at kitware.com>
> >>> wrote:
> >>>>
> >>>> I was digging into this yesterday. I'm pretty sure it is an assert
> that
> >>>> was added on that day. You have to build with Tcl and Python and
> PyInterp I
> >>>> believe to actually hit it which is still in the process of compiling
> on my
> >>>> system.
> >>>>
> >>>> On Thu, Dec 3, 2015 at 10:54 AM, Bill Lorensen <
> bill.lorensen at gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Will,
> >>>>>
> >>>>> That explains why we did not see your FlyingEdges's PrintSelfs having
> >>>>> coverage...
> >>>>>
> >>>>> On Thu, Dec 3, 2015 at 10:38 AM, Will Schroeder
> >>>>> <will.schroeder at kitware.com> wrote:
> >>>>> > Wow great catch Bill. I'm wondering how many dashboard errors are
> >>>>> > going to
> >>>>> > pop up when otherPrint comes back online....
> >>>>> >
> >>>>> > On Thu, Dec 3, 2015 at 10:12 AM, Bill Lorensen
> >>>>> > <bill.lorensen at gmail.com>
> >>>>> > wrote:
> >>>>> >>
> >>>>> >> Folks,
> >>>>> >>
> >>>>> >> We noticed that the vtk code coverage had dropped by 5% recently.
> It
> >>>>> >> turns out that the otherPrint.tcl test started to segfault around
> >>>>> >> November 23.
> >>>>> >>
> >>>>> >> Bill
> >>>>> >> _______________________________________________
> >>>>> >> 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=vtk-developers
> >>>>> >>
> >>>>> >> Follow this link to subscribe/unsubscribe:
> >>>>> >> http://public.kitware.com/mailman/listinfo/vtk-developers
> >>>>> >>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > William J. Schroeder, PhD
> >>>>> > Kitware, Inc.
> >>>>> > 28 Corporate Drive
> >>>>> > Clifton Park, NY 12065
> >>>>> > will.schroeder at kitware.com
> >>>>> > http://www.kitware.com
> >>>>> > (518) 881-4902
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Unpaid intern in BillsBasement at noware dot com
> >>>>> _______________________________________________
> >>>>> 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=vtk-developers
> >>>>>
> >>>>> Follow this link to subscribe/unsubscribe:
> >>>>> http://public.kitware.com/mailman/listinfo/vtk-developers
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Ken Martin PhD
> >>>> Chairman & CFO
> >>>> Kitware Inc.
> >>>> 28 Corporate Drive
> >>>> Clifton Park NY 12065
> >>>> 518 371 3971
> >>>>
> >>>> This communication, including all attachments, contains confidential
> and
> >>>> legally privileged information, and it is intended only for the use
> of the
> >>>> addressee.  Access to this email by anyone else is unauthorized. If
> you are
> >>>> not the intended recipient, any disclosure, copying, distribution or
> any
> >>>> action taken in reliance on it is prohibited and may be unlawful. If
> you
> >>>> received this communication in error please notify us immediately and
> >>>> destroy the original message.  Thank you.
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Ken Martin PhD
> >>> Chairman & CFO
> >>> Kitware Inc.
> >>> 28 Corporate Drive
> >>> Clifton Park NY 12065
> >>> 518 371 3971
> >>>
> >>> This communication, including all attachments, contains confidential
> and
> >>> legally privileged information, and it is intended only for the use of
> the
> >>> addressee.  Access to this email by anyone else is unauthorized. If
> you are
> >>> not the intended recipient, any disclosure, copying, distribution or
> any
> >>> action taken in reliance on it is prohibited and may be unlawful. If
> you
> >>> received this communication in error please notify us immediately and
> >>> destroy the original message.  Thank you.
> >>>
> >>> _______________________________________________
> >>> 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=vtk-developers
> >>>
> >>> Follow this link to subscribe/unsubscribe:
> >>> http://public.kitware.com/mailman/listinfo/vtk-developers
> >>>
> >>>
> >>
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20151203/abce4dc0/attachment.html>


More information about the vtk-developers mailing list