Abdelrazak Younes wrote:
> Peter Kümmel wrote:
I've found a solution without ::exit(0) which I've tested with
msvc/Qt4.2.1
and Linux/Qt4.1.3.
>>> I don't understand. Current svn doesn't need the ::exit(0) on Linux and
>>> Windows, so why is it a solution?
>>
>> It is a solution becau
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Exactly my point. With current svn, it is not necessary and everything
is destroyed in the correct order on Windows and I believe also Linux
without requiring a hard ::exit(0).
Does this mean needing ::exit(0) is a Qt bug?
I am not sure. The inter
Abdelrazak Younes wrote:
> Exactly my point. With current svn, it is not necessary and everything
> is destroyed in the correct order on Windows and I believe also Linux
> without requiring a hard ::exit(0).
Does this mean needing ::exit(0) is a Qt bug?
Peter
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it w
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>> > I suggest that you test this carefully before applying. You don't want
>>> to know how much time I spent to get it right on windows.
>>
>> Do you see/have problems with the attached patch?
>>
>> Here on windows it work
Peter Kümmel wrote:
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it works fine. It also removes the
buggy Qt code.
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
> to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it works fine. It also removes the
buggy Qt code.
Bennett, could you pl
Peter Kümmel wrote:
Should I just check in this patch:
Index: src/frontends/qt4/GuiImplementation.C
===
--- src/frontends/qt4/GuiImplementation.C (revision 15972)
+++ src/frontends/qt4/GuiImplementation.C (working copy)
On Nov 19, 2006, at 12:59 PM, Peter Kümmel wrote:
Bennett Helm wrote:
This is really a endless story. here the next try.
Well, it turns out you're wrong again: it wasn't endless! This patch
(which I applied on top of the last one) fixes the problem.
Thanks!
Bennett
Great. Good that I was
Bennett Helm wrote:
>> This is really a endless story. here the next try.
>
> Well, it turns out you're wrong again: it wasn't endless! This patch
> (which I applied on top of the last one) fixes the problem.
>
> Thanks!
>
> Bennett
>
Great. Good that I was wrong. ;)
Does it also work with th
On Nov 19, 2006, at 12:37 PM, Peter Kümmel wrote:
Bennett Helm wrote:
The crash I got was on exit, not on startup. This time I deleted
.lyxpipe.in (from another instance of LyX I had running), and
tried 1.5
again. Again, a crash on exit, but a more informative backtrace:
(gdb) run
Starting
Bennett Helm wrote:
> On Nov 19, 2006, at 12:00 PM, Abdelrazak Younes wrote:
>
>> Bennett Helm wrote:
>>> On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
>>> Thanks, Peter. Howeve
On Nov 19, 2006, at 12:00 PM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only
Bennett Helm wrote:
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only backtrace I
get:
This is not a crash on exit but on
Bennett Helm wrote:
> On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
>
>> It looks like we rely on a Qt bug on Windows and on Linux.
>> Bennett could you please try the attached patch.
>
> Thanks, Peter. However, I still get a crash. Here's the only backtrace I
> get:
>
> Starting program: /Ap
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only
backtrace I get:
Starting program: /Applications/LyX-150.app/Contents/Ma
Angus Leeming wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
Peter Kümmel wrote:
BTW, next time at a book shop, have a look at "Modern C++ Design" by
Andrei Alexandrescu.
I might do so.
Incidentally, whilst this book most definitely *is* a good investment, the
Singleton pattern was reimple
Peter Kümmel wrote:
Peter Kümmel wrote:
Peter Kümmel wrote:
Peter Kümmel wrote:
Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to us
Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
This is what I did. Hopefully, all crash-on-exit problems on windows
and Mac should be solved now.
Unfortunately, not. Quitting LyX on Mac gives:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reaso
Peter Kümmel wrote:
> Peter Kümmel wrote:
>> Peter Kümmel wrote:
>>> Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>>> Georg Baum wrote:
Peter Kümmel wrote:
>
Peter Kümmel wrote:
> Peter Kümmel wrote:
>> Bennett Helm wrote:
>>> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>>>
Georg Baum wrote:
> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>> Georg Baum wrote:
>>> Peter Kümmel wrote:
>>>
My idea was to
Peter Kümmel wrote:
> Bennett Helm wrote:
>> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>>
>>> Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
> Georg Baum wrote:
>> Peter Kümmel wrote:
>>
>>> My idea was to use some Loki code for singlet
Bennett Helm wrote:
> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>
>> Georg Baum wrote:
>>> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
> Peter Kümmel wrote:
>
>> My idea was to use some Loki code for singletons and global static
>>> dat
Angus Leeming wrote:
> Georg Baum <[EMAIL PROTECTED]> writes:
Peter Kümmel wrote:
>>> BTW, next time at a book shop, have a look at "Modern C++ Design" by
>>> Andrei Alexandrescu.
>
>> I might do so.
>
> Incidentally, whilst this book most definitely *is* a good investment, the
> Singleton
Georg Baum <[EMAIL PROTECTED]> writes:
> > > Peter Kümmel wrote:
> > BTW, next time at a book shop, have a look at "Modern C++ Design" by
> > Andrei Alexandrescu.
> I might do so.
Incidentally, whilst this book most definitely *is* a good investment, the
Singleton pattern was reimplemented as a
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to use some Loki code for singletons and global static
data.
I don't know Loki, so maybe I am missing somethi
Hello!
Maybe some help (i think i once posted it on the list): I don't have 1.5
yet so i can't test it there, but on two WinXP PCs all Versions of 1.4.3
crash also on exit if i turn on instant preview and close the lyx window
short time after opening a document (like e.g. the doc file
customi
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to use some Loki code for singletons and global static
data.
I don't know Loki, so maybe I am missing something here, but I believe
that
we already have everything
Georg Baum wrote:
> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>> Georg Baum wrote:
>>> Peter Kümmel wrote:
>>>
My idea was to use some Loki code for singletons and global static
> data.
>>> I don't know Loki, so maybe I am missing something here, but I believe
> that
>>> we a
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
> Georg Baum wrote:
> > Peter Kümmel wrote:
> >
> >> My idea was to use some Loki code for singletons and global static
data.
> >
> > I don't know Loki, so maybe I am missing something here, but I believe
that
> > we already have everyth
On Fri, Nov 17, 2006 at 04:57:14PM +0100, Peter Kümmel wrote:
> > Abdelrazak> This is something else... Do you have an idea Georg?
> >
> > Looks like prepareExit tries to use _() and the iconv stuff has
> > already been killed. Probably that the static IconvProcessor (in
> > utf8_to_ucs4) and the
Peter Kümmel wrote:
Abdelrazak Younes wrote:
avoid global static data!
Yes, maybe the remaining data could be centralized in one class which will
be create and deleted at one place. We should avoid that creation and
destruction is handled automatically by the compiler.
What do you think I
On Nov 17, 2006, at 11:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's
Georg Baum wrote:
> Peter Kümmel wrote:
>
>> My idea was to use some Loki code for singletons and global static data.
>
> I don't know Loki, so maybe I am missing something here, but I believe that
> we already have everything needed.
Yes, we have C++.
BTW, next time at a book shop, have a look
Peter Kümmel wrote:
> My idea was to use some Loki code for singletons and global static data.
I don't know Loki, so maybe I am missing something here, but I believe that
we already have everything needed.
>> avoid global static data!
>
> Yes, maybe the remaining data could be centralized in
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>>> Abdelrazak> Bennett Helm wrote:
> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Please try again with last svn.
Ab
Peter Kümmel wrote:
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
Jean-Marc Lasgouttes wrote:
>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Abdelrazak> Bennett Helm wrote:
>>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
> backtr
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new bac
Abdelrazak Younes wrote:
> Bennett Helm wrote:
>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>>
>>> Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
>>>
>>> Could you try out this patch please?
>>
>> I still get a crash. Here's the
Jean-Marc Lasgouttes wrote:
> Looks like prepareExit tries to use _() and the iconv stuff has
> already been killed. Probably that the static IconvProcessor (in
> utf8_to_ucs4) and the LyX instance are not deleted in the right order.
That was exactly the result of my analysis, too.
Georg
On Nov 17, 2006, at 10:32 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out t
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>>> Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
>>> Could you try out this patc
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCESS, Could not access
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the backtrace:
Could you try out this patch please?
Thanks in advance,
Abdel.
Index: lyx_main.C
===
--- lyx_main.C (revision 15953)
+++ lyx_main.C
Peter Kümmel wrote:
> Sorry for not having fixed a bug which I've not introduced.
No need to be sorry. I am only a bit frustrated that probably the same bug
comes again and again.
Georg
Abdelrazak Younes wrote:
> Looks like I am responsible here but I don't regret anything. I will
> review this code and solve the problem before 1.5.0.
Fine.
Georg
Georg Baum wrote:
Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in ra
On Thursday 16 November 2006 11:40 pm, Peter Kümmel wrote:
> Sorry for not having fixed a bug which I've not introduced.
Don't worry I forgive you. ;-) (Only 7 minutes remains to be so magnanimous)
> Regards,
> Peter
--
José Abílio
Georg Baum wrote:
> Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
> backtrace:
>>> Program received signal SIGABRT, Aborted.
>>> 0x9003d1dc in kill ()
>>> (gdb) bt
>>> #0 0x9003d1dc in kill (
Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
> Bennett Helm wrote:
> > 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
> >
> > Program received signal SIGABRT, Aborted.
> > 0x9003d1dc in kill ()
> > (gdb) bt
> > #0 0x9003d1dc in kill ()
> > #1 0x9010f2
On Nov 16, 2006, at 12:46 PM, Peter Kümmel wrote:
Bennett Helm wrote:
On Nov 16, 2006, at 6:41 AM, Peter Kümmel wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0
Bennett Helm wrote:
> On Nov 16, 2006, at 6:41 AM, Peter Kümmel wrote:
>
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
>>> backtrace:
>>>
>>> Program received signal SIGABRT, Aborted.
>>> 0x9003d1dc in kill ()
>>> (gdb) bt
>>> #0 0x9003d1dc in kill ()
On Nov 16, 2006, at 6:41 AM, Peter Kümmel wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in raise ()
#2 0x9010de02 in abor
Bennett Helm wrote:
> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the backtrace:
>
> Program received signal SIGABRT, Aborted.
> 0x9003d1dc in kill ()
> (gdb) bt
> #0 0x9003d1dc in kill ()
> #1 0x9010f2af in raise ()
> #2 0x9010de02 in abort ()
> #3 0x90b4039c in __gnu_cxx::__v
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in raise ()
#2 0x9010de02 in abort ()
#3 0x90b4039c in __gnu_cxx::__verbose_terminate_handler ()
#4 0x9
61 matches
Mail list logo
