[vtkusers] vtkTextActor segfaults my render window
Jérôme
jerome.velut at gmail.com
Thu Dec 10 03:31:57 EST 2009
I *really* have to integrate valgrind in my debugging process! Thanks for
the reminder, Bill. I put a log file here :
http://jerome.velut.free.fr/transfert/DrawText-valgrind-output2552 (Too big
for the list, 'had to cancel the previous post...)
It has been obtained with your command line, except that --num-callers has
to be between 0 and 50 (claimed valgrind at first exec). I also add
--log-file=DrawText-valgring-output%p to catch the output.
It ends on a segfault, that is not logged into the file, I think:
------------------------------------------------------------------------------------------
[dje at Djelaptop build]$ valgrind --trace-children=yes --quiet
--tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=50
--verbose --demangle=yes --log-file=DrawText-valgring-output%p ./DrawText
Erreur de segmentation (core dumped)
------------------------------------------------------------------------------------------
I found back the gdb backtrace concerning vtk_freetype_FTC_CMapCache_Lookup,
in a "Invalid read of size 4" section. I let you look into the log file,
since I don't know much about that!
2009/12/9 Bill Lorensen <bill.lorensen at gmail.com>
> Have you tried running the example with valgrind?
>
> valgrind --trace-children=yes --quiet --tool=memcheck
> --leak-check=yes --show-reachable=yes --num-callers=100 --verbose
> --demangle=yes ./DrawText
>
> On Wed, Dec 9, 2009 at 4:57 PM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
> > I see. It is linking against the paraview version of VTK. That's what
> > threw me. When I run David's example against VTK head, it runs fine.
> >
> > Maybe someone with a paraview vtk can try the example?
> >
> > Bill
> >
> > On Wed, Dec 9, 2009 at 4:52 PM, Jérôme <jerome.velut at gmail.com> wrote:
> >> Bill,
> >>
> >> this is the one I posted previously. I hope it is helpful? I was
> checking
> >> the dashboard for failed tests, but I am simply lost in all these
> results...
> >>
> >> Thanks for your interest!
> >>
> >> Jerome
> >>
> >> 2009/12/9 Bill Lorensen <bill.lorensen at gmail.com>
> >>>
> >>> What traceback do you get with David's example?
> >>>
> >>> On Wed, Dec 9, 2009 at 4:29 PM, Jérôme <jerome.velut at gmail.com> wrote:
> >>> > Continuing my investigation. It seems I am alone with that problem.
> >>> > David Doria kindly put an example of a use-case of vtkTextActor on
> the
> >>> > wiki:
> >>> > http://www.cmake.org/Wiki/Display_text
> >>> >
> >>> > I confirm my segfault with that code, only when linking to VTK built
> in
> >>> > release. It does not make difference if my code is complied Debug or
> >>> > Release.
> >>> >
> >>> > Here is the gdb backtrace:
> >>> > (gdb) bt
> >>> > #0 0x005f7a72 in vtk_freetype_FTC_CMapCache_Lookup ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkfreetype.so.pv3.7
> >>> > #1 0x009830bc in vtkFreeTypeUtilities::GetGlyphIndex(unsigned long,
> >>> > char,
> >>> > unsigned int*) ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #2 0x00987b50 in
> vtkFreeTypeUtilities::GetBoundingBox(vtkTextProperty*,
> >>> > char const*, int*) ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #3 0x009883dd in
> vtkFreeTypeUtilities::PrepareImageData(vtkImageData*,
> >>> > vtkTextProperty*, char const*, int*, int*) ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #4 0x009888fe in
> vtkFreeTypeUtilities::RenderString(vtkTextProperty*,
> >>> > char
> >>> > const*, vtkImageData*) ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #5 0x00946e3e in vtkTextActor::RenderOpaqueGeometry(vtkViewport*) ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #6 0x008f87a6 in vtkRenderer::UpdateGeometry() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #7 0x009cf547 in vtkOpenGLRenderer::DeviceRender() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #8 0x008f91fb in vtkRenderer::Render() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #9 0x008f4b7b in vtkRendererCollection::Render() ()
> >>> > ---Type <return> to continue, or q <return> to quit---
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #10 0x0090789f in vtkRenderWindow::DoStereoRender() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #11 0x00907c80 in vtkRenderWindow::DoFDRender() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #12 0x009090ab in vtkRenderWindow::DoAARender() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #13 0x00907dc5 in vtkRenderWindow::Render() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #14 0x00a0d184 in vtkXOpenGLRenderWindow::Render() ()
> >>> > from
> >>> > /home/dje/Softwares/ParaView-3.7/Release/bin/libvtkRendering.so.pv3.7
> >>> > #15 0x08049c1b in main () at
> /home/dje/Codes/TestFilter/DrawText.cxx:50
> >>> >
> >>> >
> >>> > For now, I am working with ParaView/VTK in Debug built. But I hope
> >>> > someone
> >>> > will explain me what is the trouble with my release builds.
> >>> >
> >>> > Jerome
> >>> >
> >>> > 2009/12/9 Jérôme <jerome.velut at gmail.com>
> >>> >>
> >>> >> I just compiled ParaView/VTK in Debug mode, the problem
> disappears...
> >>> >> So I
> >>> >> can be more precise about the reproducibility check:
> >>> >> Could you tell me if you have a segfault with really simple script
> in
> >>> >> a
> >>> >> linux (F12) release built?
> >>> >>
> >>> >> Thanks again,
> >>> >> Jerome
> >>> >>
> >>> >> 2009/12/8 Jérôme <jerome.velut at gmail.com>
> >>> >>>
> >>> >>> Dear all,
> >>> >>> It seems that I misused the vtkTextActor for a while: a recent CVS
> >>> >>> checkout makes a simple vtkTextActor rendering crashing by seg
> fault.
> >>> >>> I
> >>> >>> noted this error inside a ParaView cxx plugin, but now I have
> isolated
> >>> >>> the
> >>> >>> cause: A vtkTextActor added to the renderer yields the crash.
> >>> >>>
> >>> >>> Please, find attach a python script that reproduces the bug (by me,
> at
> >>> >>> least... my settings may be guilty). Could you tell me if you have
> >>> >>> such an
> >>> >>> error, and if my way of using text actor is wrong?
> >>> >>>
> >>> >>> Thanks a lot!
> >>> >>>
> >>> >>> Jerome
> >>> >>
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > Powered by www.kitware.com
> >>> >
> >>> > Visit other Kitware open-source projects at
> >>> > http://www.kitware.com/opensource/opensource.html
> >>> >
> >>> > Please keep messages on-topic and check the VTK FAQ at:
> >>> > http://www.vtk.org/Wiki/VTK_FAQ
> >>> >
> >>> > Follow this link to subscribe/unsubscribe:
> >>> > http://www.vtk.org/mailman/listinfo/vtkusers
> >>> >
> >>> >
> >>
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20091210/ec43cf54/attachment.htm>
More information about the vtkusers
mailing list