Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#46903 - [texstudio] 2.10.x segfaults on start

Attached to Project: Community Packages
Opened by Bernd Prünster (JesusMcCloud) - Wednesday, 28 October 2015, 21:19 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 13 February 2016, 17:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Texstudio does not start, but segfaults shortly after launch. Running it through gdb (sometimes) yields:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4d9b856 in __gnu_cxx::__exchange_and_add (__val=-1, __mem=0x28206e616d72653f)
at /build/gcc-multilib/src/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/ext/atomicity.h:49
49 /build/gcc-multilib/src/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/ext/atomicity.h: No such file or directory.

This happens not only for v2.10.4, but also for versions which previously worked, such as 2.10.2 (even after recompiling).
It does not matter whether texstudio is built against Qt4 or Qt5. Other versions and other packages may also be affected.

I am sorry for not being able to provide more detailed info. I just ran into this after a full system upgrade. I don't suspect texstudio to be the cause of the problem, but rather the only symptom I was able to observe.

Additional info:
* package version(s):
texstudio 2.10.x
lib32-libstdc++5 3.3.6-7

Steps to reproduce:
Launch texstudio using gdb. Roughly every other time the output shown above is produced.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 13 February 2016, 17:46 GMT
Reason for closing:  Fixed
Comment by Bernd Prünster (JesusMcCloud) - Friday, 30 October 2015, 06:18 GMT
It turns out, this bug must have been introduced at least two weeks before I reported it (another system, which is not fully up to date, is also affected). Again, I'm really sorry for not being able to provide more precise information.
Comment by Bernd Prünster (JesusMcCloud) - Friday, 30 October 2015, 08:06 GMT
Pacman log of the update which caused the problem.
   pacman.log (9.3 KiB)
Comment by Felix Schmidt (felux) - Monday, 02 November 2015, 10:06 GMT
Hello, I'm new in reporting bugs. Unfortunately, I can confirm the bug above. I think all versions of texstudio above 2.10.* are affected - none of them were able to open any of my tex files. In my setup I got the seqmentation fault right after opening any .tex-file. I attached a gdb log and a texstudio backtrace.
   texstudio_gdb.log (0.8 KiB)
   texstudio_backtrace1.txt (0.1 KiB)
Comment by Bernd Prünster (JesusMcCloud) - Monday, 02 November 2015, 17:44 GMT
FYI texstudio 2.9.4 (built against qt4) seems to run fine
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 24 November 2015, 07:43 GMT
Still can't reproduce. Sounds like a processor/compiler thing. I'm on an Intel i5-4670K. What are you guys using?
Comment by Bernd Prünster (JesusMcCloud) - Tuesday, 24 November 2015, 08:59 GMT
I actually have two machines which are affected:
One Sandy Bridge i3 (i3-2xxxM) and one Ivy Bridge i3 (i3-3xxxM), both running the 64 bit variant of Arch Linux.
Comment by Shimi Chen (shimi) - Thursday, 26 November 2015, 09:14 GMT
Same issue here. TeXstudio>=2.10 crashes when opening any file with:
“texstudio” terminated by signal SIGSEGV (Address boundary error)

Only workaround: downgrade package to 2.9.4-3.
64 bit architecture.
CPU version: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
Comment by Bernd Prünster (JesusMcCloud) - Friday, 27 November 2015, 22:57 GMT
Building with -O0 seems to fix this for me.
Comment by Bernd Prünster (JesusMcCloud) - Friday, 11 December 2015, 14:14 GMT
It seems that building with -O0 is not a sufficient work-around. Sometimes (sadly, I have absolutely no clue when and why) texstudio still segfaults on start and remains unusable until some time later it miraculously starts working again.

I am happy to help and provide more info of any kind. However, I don't really know how. If there are specific tasks I can perform to assist in hunting down this problem, please let me know.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 11 December 2015, 17:17 GMT
Please test with the new gcc 5.3 built package.
Comment by Bernd Prünster (JesusMcCloud) - Saturday, 12 December 2015, 14:36 GMT
Now not even 2.9.4 works anymore (crashes just like 2.10)

Edit: 2.9.2 seems to work.
This is continuously getting weirder...
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 22 December 2015, 08:15 GMT
Please report this upstream and post a link to the report here. This issue is too weird for us to track down here.
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 13 February 2016, 13:21 GMT
What is the status here?
Comment by Bernd Prünster (JesusMcCloud) - Saturday, 13 February 2016, 16:08 GMT
I'm terribly sorry for just disappearing; I've never been as busy as I was during the past weeks.
Good news is, it seems to have resolved itself after today's update!

Loading...