Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: On 11/20/2014 07:07 PM, Cyrille Artho wrote: To those who did not think they observed the crashes: Such crashes may be rare (1 in 100,000 uses), so unless you are looking for them and force them to occur with tool support, you are not going to notice this in everyday use. A

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/20/2014 07:07 PM, Cyrille Artho wrote: To those who did not think they observed the crashes: Such crashes may be rare (1 in 100,000 uses), so unless you are looking for them and force them to occur with tool support, you are not going to notice this in everyday use. A random crash every c

Re: Thread problems with std::basic_string and GNU libstdc++

Georg Baum wrote: Hi, while investigating http://www.lyx.org/trac/ticket/9336 I found out a fundamental problem with our multithreaded export: The GNU libstdc++ gives only a relatively weak thread-safety guarantee about std::basic string. It is not completely thread-safe in the POSIX sense. The

Re: Thread problems with std::basic_string and GNU libstdc++

On Thu, Nov 20, 2014 at 09:04:39PM +0100, Georg Baum wrote: > Abdelrazak Younes wrote: > > I believe that there could be many reasons that could cause a crash > > before incriminating the stl string, etc: > > * Gui elements (message passing?) > > * Graphics preview elements > > I don't think so in

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: > I'm on Fedora 20, which has gcc 4.8.3. I have gcc 4.7.2. > Scott mentioned something there. I see. I installed pLyX, but I fear my way of thinking is very different from the one in the pLyX system. At least I did not manage to get it to do what I want. Georg

Re: Python 3 incompatibilities still exist right?

On Thu, Nov 20, 2014 at 11:36 AM, Richard Heck wrote: > On 11/20/2014 09:55 AM, stefano franchi wrote: > > On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak wrote: > >> I cleaned RELEASE-NOTES for the master branch. This note is still >> relevant right? >> >> - LyX needs to be run under Python 2

Re: Thread problems with std::basic_string and GNU libstdc++

Abdelrazak Younes wrote: > Hi Georg, > > Warning: I haven't read LyX source code for a long long time :-) This is no problem, I think the main point can be understood quite well without code details. > I am not questioning your reasoning but I think STL thread safety > limitation has limited i

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/20/2014 02:39 PM, Abdelrazak Younes wrote: Hi Georg, Warning: I haven't read LyX source code for a long long time :-) On 19/11/2014 22:43, Georg Baum wrote: Hi, while investigating http://www.lyx.org/trac/ticket/9336 I found out a fundamental problem with our multithreaded export: The G

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/20/2014 02:35 PM, Georg Baum wrote: Richard Heck wrote: I'm not well informed enough about implementation details to have an opinion about whether this diagnosis is correct. But I am somewhat puzzled that we are only seeing this issue now. Of course, there may have been other random crash

Re: Thread problems with std::basic_string and GNU libstdc++

Hi Georg, Warning: I haven't read LyX source code for a long long time :-) On 19/11/2014 22:43, Georg Baum wrote: Hi, while investigating http://www.lyx.org/trac/ticket/9336 I found out a fundamental problem with our multithreaded export: The GNU libstdc++ gives only a relatively weak thread-s

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: > I'm not well informed enough about implementation details to have an > opinion about whether this > diagnosis is correct. But I am somewhat puzzled that we are only seeing > this issue now. Of course, > there may have been other random crashes that people haven't reported. T

Re: Python 3 incompatibilities still exist right?

On 11/20/2014 09:55 AM, stefano franchi wrote: On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak > wrote: I cleaned RELEASE-NOTES for the master branch. This note is still relevant right? - LyX needs to be run under Python 2 and will not work properly on

Re: Python 3 incompatibilities still exist right?

The incompatibilities still exist at least in Windows sistems, since LyX installer bundles a python distribution itself and creates a conflict when python3 is the default. Moreover you cannot use python3 within LyX in Windows, because you will beak the system, LyX will not reconfigure anymore!! Jus

Re: Python 3 incompatibilities still exist right?

On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak wrote: > I cleaned RELEASE-NOTES for the master branch. This note is still > relevant right? > > - LyX needs to be run under Python 2 and will not work properly on systems > where Python 3 is the default binary. See bug #7030 to know how to fix >

Re: Help with patch for "word selection mode" on double click

On Tue, Oct 28, 2014 at 7:03 AM, Scott Kostyshak wrote: > I have a patch that enables "word selection mode" on double click. It > seems to work well. The patch is here: > > http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch > > The only major issue is that when dragging to

Re: Clear RELEASE-NOTES on master?

On Tue, Nov 18, 2014 at 3:05 AM, Jean-Marc Lasgouttes wrote: > Le 18/11/14 02:14, Scott Kostyshak a écrit : >> >> The RELEASE-NOTES on master is for 2.1.0. Should it be cleaned so we >> can add 2.2.0 stuff or is this done somewhere else that I forgot? I >> can do the work but I wanted to check in

Python 3 incompatibilities still exist right?

I cleaned RELEASE-NOTES for the master branch. This note is still relevant right? - LyX needs to be run under Python 2 and will not work properly on systems where Python 3 is the default binary. See bug #7030 to know how to fix this properly, since simple sheebang conversion in *.py files will