Menu ▾ ▴

#116 3.1.x segfaults on --fork

Next_release
closed
nobody
None
1
2018-09-28
2015-08-20
Anonymous
No

Reported on the Arch Linux Bugtracker
https://bugs.archlinux.org/task/46034

The user reports, that using --fork isn't working that well for him with the 3.1.x (3.1.3 and 3.1.4) series, whereas 3.0.x had no problems

Discussion

  • Anonymous

    Anonymous - 2015-08-20

    I reported this on the ArchLinux Bugtracker.

     

  • Tony Houghton

    Tony Houghton - 2015-08-20

    Fixed in 3.1.5.

     

  • Tony Houghton

    Tony Houghton - 2015-08-20
    • status: open --> closed
     

  • Anonymous

    Anonymous - 2018-09-28

    I have the same problem with version 3.6.1

    [ 1142.501596] roxterm[5858]: segfault at 18 ip 000055f1bfa90840 sp 00007ffc68533108 error 4 in roxterm[55f1bfa7c000+3a000]
[ 1219.175970] roxterm[9111]: segfault at 81 ip 00007f6f0518c91d sp 00007ffc91ce0360 error 4 in libglib-2.0.so.0.5800.0[7f6f05159000+82000]
     

    • Tony Houghton

      Tony Houghton - 2018-09-28

      I can't reproduce this here. Is it definitely triggered by --fork? The latest version of VTE caused a new bug which crashes all roxterm tabs/windows when you close one with the GUI, which I fixed in 3.7.2. If it isn't that please report this on github with exact steps to reproduce the problem. If you have debugging symbols available and can get a backtrace with gdb that would be great. The easiest way to do that is to run ./AppRun --debug, which will also build it first if necessary, but you may need to install some extra packages for the headers etc it needs.

       

  • Anonymous

    Anonymous - 2018-09-28

    The latest version of VTE caused a new bug which crashes all roxterm tabs/windows when you close one with the GUI, which I fixed in 3.7.2

    That seems to be the problem indeed. I build 3.7.2 and everything run smoot again. Thanks

     

Anonymous
Anonymous

Add attachments
Cancel