segmentation fault when opening xplt in postview for second time (glibc 2.19)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • jpeloquin
    Junior Member
    • Mar 2012
    • 12

    segmentation fault when opening xplt in postview for second time (glibc 2.19)

    After opening an xplt file in postview, opening another xplt file (or reopening the same file) causes a segmentation fault.

    I have observed the segementation fault when running PostView 1.7.0 (x64), 1.8.0 (x64, glibc compiled with 2.17), and 1.8.0 (x32) on Linux. The segmentation fault does not occur under Windows.

    This issue (or one with identical symptoms) was previously reported in the following thread:



    In that case, the thread was resolved with a workaround: use a different system with glibc 2.12. I am starting this thread in the hopes of obtaining a solution that does not require the use of an older operating system.

    Relevant information for the system on which the segmentation fault occurs:

    Code:
    $ uname -a
    Linux dmelab-peloquin 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    
    $ /lib/x86_64-linux-gnu/libc.so.6 
    GNU C Library (Ubuntu EGLIBC 2.19-0ubuntu6.5) stable release version 2.19, by Roland McGrath et al.
    Copyright (C) 2014 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.
    There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
    PARTICULAR PURPOSE.
    Compiled by GNU CC version 4.8.2.
    Compiled on a Linux 3.13.11 system on 2014-12-04.
    Available extensions:
    	crypt add-on version 2.1 by Michael Glad and others
    	GNU Libidn by Simon Josefsson
    	Native POSIX Threads Library by Ulrich Drepper et al
    	BIND-8.2.3-T5B
    libc ABIs: UNIQUE IFUNC
    For bug reporting instructions, please see:
    <https://bugs.launchpad.net/ubuntu/+source/eglibc/+bugs>.
    The last couple of lines output by `strace postview` are:

    Code:
    munmap(0x7fe197e18000, 6885376)         = 0
    munmap(0x7fe198b3a000, 1204224)         = 0
    --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
    +++ killed by SIGSEGV (core dumped) +++
    I can provide the full output if it would be useful.

    The following backtrace is provided by running gdb on a core dump (PostView 1.7.0 x64):

    Code:
    #0  0x00007f11cb27b54d in fclose () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x000000000050bcbb in FEFileImport::~FEFileImport() ()
    #2  0x000000000048d372 in FEBioPlotImport::~FEBioPlotImport() ()
    #3  0x000000000045d3f5 in CDocument::LoadProject(FEFileImport*, char const*, bool) ()
    #4  0x000000000055d953 in CWnd::OnFileOpen(Fl_Widget*, void*) ()
    #5  0x00000000005e0685 in Fl_Widget::do_callback(Fl_Widget*, void*) ()
    #6  0x00000000005bbcf2 in Fl_Button::handle(int) ()
    #7  0x00000000005b6e08 in send(int, Fl_Widget*, Fl_Window*) ()
    #8  0x00000000005b7913 in Fl::handle_(int, Fl_Window*) ()
    #9  0x00000000005e5385 in fl_handle(_XEvent const&) ()
    #10 0x00000000005e5468 in do_queued_events() ()
    #11 0x00000000005e55d7 in fl_wait(double) ()
    #12 0x00000000005b8473 in Fl::wait(double) ()
    #13 0x00000000005b84d3 in Fl::run() ()
    #14 0x00000000005ab547 in main ()
    Since the SIGSEGV si_addr is 0, I am speculating that fclose() was called on NULL, but I could very easily be wrong.

    I am happy to provide further information if it would be helpful.


    Best regards,

    John Peloquin
    --
    John Peloquin, PhD
    University of Delaware
    peloquin@udel.edu
  • jpeloquin
    Junior Member
    • Mar 2012
    • 12

    #2
    I did some more investigation about whether this is caused by glibc version mismatch. I tried the postview 1.8.0.6510 x64 (glibc 2.17) binary on an Ubuntu 13 virtual machine and a CentOS 7 virtual machine. Both distributions use glibc 2.17, so there should be no mismatch with the binary. The issue described above was reproduced on both machines.
    --
    John Peloquin, PhD
    University of Delaware
    peloquin@udel.edu

    Comment

    • dsrawlins
      Developer
      • Dec 2008
      • 366

      #3
      Hi John,

      This bug has been fixed and will be updated in the next release version of PostView.

      Best,

      Dave
      Department of Bioengineering, University of Utah
      Scientific Computing and Imaging institute, University of Utah

      Comment

      • dsrawlins
        Developer
        • Dec 2008
        • 366

        #4
        John,

        I've updated the Linux 64bit download to version 1.8.3, which includes this fix.

        Best,

        Dave
        Department of Bioengineering, University of Utah
        Scientific Computing and Imaging institute, University of Utah

        Comment

        Working...
        X
        😀
        😂
        🥰
        😘
        🤢
        😎
        😞
        😡
        👍
        👎