On Wed, May 31, 2006 at 10:45:00AM +0200, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre Are we really explicitly calling exit()?
Yes, in lyx_gui::exit, which is called in quitLyX. Do you think this
is a problem?
I am not sure this is an a_actual_
Am Dienstag, 6. Juni 2006 18:41 schrieb Andre Poenitz:
On Wed, May 31, 2006 at 10:45:00AM +0200, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz
[EMAIL PROTECTED] writes:
Andre Are we really explicitly calling exit()?
Yes, in lyx_gui::exit, which is called in quitLyX. Do you
On Sat, Jun 03, 2006 at 02:41:51PM +0200, Georg Baum wrote:
possible. It turned out that the pointer solution did not really work
(apart from the exception safety which is not so important because we
have already the lyxsocket and lyxserver pointers)
Okokok.
Andre'
On Wed, May 31, 2006 at 10:45:00AM +0200, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Andre> Are we really explicitly calling exit()?
>
> Yes, in lyx_gui::exit, which is called in quitLyX. Do you think this
> is a problem?
I am not sure this is
Am Dienstag, 6. Juni 2006 18:41 schrieb Andre Poenitz:
> On Wed, May 31, 2006 at 10:45:00AM +0200, Jean-Marc Lasgouttes wrote:
> > > "Andre" == Andre Poenitz
<[EMAIL PROTECTED]> writes:
> >
> > Andre> Are we really explicitly calling exit()?
> >
> > Yes, in lyx_gui::exit, which is called in
On Sat, Jun 03, 2006 at 02:41:51PM +0200, Georg Baum wrote:
> possible. It turned out that the pointer solution did not really work
> (apart from the exception safety which is not so important because we
> have already the lyxsocket and lyxserver pointers)
Okokok.
Andre'
Am Dienstag, 30. Mai 2006 18:06 schrieb Andre Poenitz:
Is this a extreme-trial-and-error-ing contest?
No. It is the attempt to find out how to fit QApplication into the GUII
framework in such a way that it does not crash on OS X (and I know what
you will now answer).
If so, this should be
Georg Baum wrote:
Am Dienstag, 30. Mai 2006 18:06 schrieb Andre Poenitz:
without a static object and without new/delete? This is impossible AFAIK,
therefore I am currently reorganizing the startup mechanism to make
What are you doing exactly? FYI I am completely reorganizing lyx_gui and
Am Dienstag, 30. Mai 2006 18:06 schrieb Andre Poenitz:
> Is this a extreme-trial-and-error-ing contest?
No. It is the attempt to find out how to fit QApplication into the GUII
framework in such a way that it does not crash on OS X (and I know what
you will now answer).
> If so, this should be
Georg Baum wrote:
Am Dienstag, 30. Mai 2006 18:06 schrieb Andre Poenitz:
without a static object and without new/delete? This is impossible AFAIK,
therefore I am currently reorganizing the startup mechanism to make
What are you doing exactly? FYI I am completely reorganizing lyx_gui and
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre Are we really explicitly calling exit()?
Yes, in lyx_gui::exit, which is called in quitLyX. Do you think this
is a problem?
JMarc
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak + Since the QApplication object does so much
Abdelrazak initialization, it + must be created before any other
Abdelrazak objects related to the user + interface are created.
Abdelrazak + Right now this is not the case. For
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log
to the .C file. Otherwise it is easy to get forgotten.
Abdelrazak Done.
Also, could someone
Jean-Marc Lasgouttes wrote:
Also, could someone tell me what would be a good candidate to fix the
crash in Mac/qt3 for 1.4? I am lost in this thread.
When do you want to release? I have an idea, but it needs some thinking. If
it can wait until the weekend I can create a patch.
Georg
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak + Since the QApplication object does so much
Abdelrazak initialization, it + must be created before any other
Abdelrazak objects related to the user + interface are created.
Abdelrazak + Right now
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log
to the .C file. Otherwise it is easy to get forgotten.
Abdelrazak Younes wrote:
it could be _one_ problem. The static versus pointer code proves that
the same code is translated differently by gcc in linux and windows.
How does it prove that? I suspect that we simply see the code differences
between the windows and linux version of qt.
Georg
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak This is a static method of FontLoader and I suspect that
Abdelrazak it needs at least an instantiation of this class.
It does not (because it is static). Anyway there _is_ a global
fontloader object, but its constructor does
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg When do you want to release? I have an idea, but it needs some
Georg thinking. If it can wait until the weekend I can create a
Georg patch.
I do not have plans yet. It will not be before next week in any case.
JMarc
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak This is a static method of FontLoader and I suspect that
Abdelrazak it needs at least an instantiation of this class.
It does not (because it is static). Anyway there _is_ a global
fontloader
Georg Baum wrote:
Abdelrazak Younes wrote:
it could be _one_ problem. The static versus pointer code proves that
the same code is translated differently by gcc in linux and windows.
How does it prove that? I suspect that we simply see the code differences
between the windows and linux
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> Are we really explicitly calling exit()?
Yes, in lyx_gui::exit, which is called in quitLyX. Do you think this
is a problem?
JMarc
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> + Since the QApplication object does so much
Abdelrazak> initialization, it + must be created before any other
Abdelrazak> objects related to the user + interface are created.
Abdelrazak> + Right now this is not the
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Georg Baum wrote:
>> Abdelrazak Younes wrote:
>>> Will commit now.
>> It would be nice if you could add the comment from your commit log
>> to the .C file. Otherwise it is easy to get forgotten.
Abdelrazak> Done.
Jean-Marc Lasgouttes wrote:
> Also, could someone tell me what would be a good candidate to fix the
> crash in Mac/qt3 for 1.4? I am lost in this thread.
When do you want to release? I have an idea, but it needs some thinking. If
it can wait until the weekend I can create a patch.
Georg
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> + Since the QApplication object does so much
Abdelrazak> initialization, it + must be created before any other
Abdelrazak> objects related to the user + interface are created.
Abdelrazak> +
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log
to the .C file. Otherwise it is easy to get forgotten.
Abdelrazak Younes wrote:
> it could be _one_ problem. The static versus pointer code proves that
> the same code is translated differently by gcc in linux and windows.
How does it prove that? I suspect that we simply see the code differences
between the windows and linux version of qt.
Georg
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> This is a static method of FontLoader and I suspect that
Abdelrazak> it needs at least an instantiation of this class.
It does not (because it is static). Anyway there _is_ a global
fontloader object, but its
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> When do you want to release? I have an idea, but it needs some
Georg> thinking. If it can wait until the weekend I can create a
Georg> patch.
I do not have plans yet. It will not be before next week in any case.
JMarc
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> This is a static method of FontLoader and I suspect that
Abdelrazak> it needs at least an instantiation of this class.
It does not (because it is static). Anyway there _is_ a global
Georg Baum wrote:
Abdelrazak Younes wrote:
it could be _one_ problem. The static versus pointer code proves that
the same code is translated differently by gcc in linux and windows.
How does it prove that? I suspect that we simply see the code differences
between the windows and linux
On Sat, May 27, 2006 at 04:02:33PM +0200, Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:40 schrieb Abdelrazak Younes:
OK, then this patch use a straight QApplication. QLApplication is used
only for Mac as far as I see. And use qApp only.
Does not help:
#0 0xb7b94bcc in
On Sat, May 27, 2006 at 03:20:36PM +0200, Abdelrazak Younes wrote:
Georg Baum wrote:
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
Abdel, do you have any idea why this happens?
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this
On Sat, May 27, 2006 at 03:40:55PM +0200, Abdelrazak Younes wrote:
Index: lyx_gui.C
===
--- lyx_gui.C (revision 13933)
+++ lyx_gui.C (working copy)
@@ -112,7 +112,7 @@
{
public:
LQApplication(int argc, char ** argv);
Andre Poenitz wrote:
On Sat, May 27, 2006 at 04:02:33PM +0200, Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:40 schrieb Abdelrazak Younes:
OK, then this patch use a straight QApplication. QLApplication is used
only for Mac as far as I see. And use qApp only.
Does not help:
#0 0xb7b94bcc in
Andre Poenitz wrote:
- static LQApplication app(argc, argv);
+ static QApplication app(argc, argv);
Why static?
Because it's inside a function (parse_init). It cannot be made a global
variable due to the necessity to pass argc and argv at the construction.
Abdel.
Andre Poenitz wrote:
-LQApplication::~LQApplication()
-{}
+//LQApplication::~LQApplication()
+//{}
The compiler creates comething identical to this if there is no
destructor defined.
[Which means, that the change as such is good as it removes useless
code, but there should not be any visible
On Sat, May 27, 2006 at 04:29:15PM +0200, Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor.
This was the right idea. The
On Sat, May 27, 2006 at 04:02:33PM +0200, Georg Baum wrote:
> Am Samstag, 27. Mai 2006 15:40 schrieb Abdelrazak Younes:
> > OK, then this patch use a straight QApplication. QLApplication is used
> > only for Mac as far as I see. And use qApp only.
>
> Does not help:
>
> #0 0xb7b94bcc in
On Sat, May 27, 2006 at 03:20:36PM +0200, Abdelrazak Younes wrote:
> Georg Baum wrote:
> >Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
>
> >Abdel, do you have any idea why this happens?
>
> Another idea... Maybe the QApplication destruction is happening too soon
> in the exit process,
On Sat, May 27, 2006 at 03:40:55PM +0200, Abdelrazak Younes wrote:
> Index: lyx_gui.C
> ===
> --- lyx_gui.C (revision 13933)
> +++ lyx_gui.C (working copy)
> @@ -112,7 +112,7 @@
> {
> public:
> LQApplication(int & argc, char
Andre Poenitz wrote:
On Sat, May 27, 2006 at 04:02:33PM +0200, Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:40 schrieb Abdelrazak Younes:
OK, then this patch use a straight QApplication. QLApplication is used
only for Mac as far as I see. And use qApp only.
Does not help:
#0 0xb7b94bcc in
Andre Poenitz wrote:
- static LQApplication app(argc, argv);
+ static QApplication app(argc, argv);
Why static?
Because it's inside a function (parse_init). It cannot be made a global
variable due to the necessity to pass argc and argv at the construction.
Abdel.
Andre Poenitz wrote:
-LQApplication::~LQApplication()
-{}
+//LQApplication::~LQApplication()
+//{}
The compiler creates comething identical to this if there is no
destructor defined.
[Which means, that the change as such is good as it removes useless
code, but there should not be any visible
On Sat, May 27, 2006 at 04:29:15PM +0200, Georg Baum wrote:
> Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
> > Another idea... Maybe the QApplication destruction is happening too soon
> > in the exit process, this patch remove the QLApplication destructor.
>
> This was the right
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
Georg
Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
You're right, I'll do that. This reminds me of some feature requests for
SVN:
1) in lyx.cvs list, put an
Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
Done.
Abdel.
Index: lyx_gui.C
===
---
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get: lyx: SIGSEGV signal caught Sorry, you
have found a bug in LyX. Please read the bug-reporting instructions
in Help-Introduction and send us a bug report, if
Jean-Marc Lasgouttes wrote:
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get: lyx: SIGSEGV signal caught Sorry, you
have found a bug in LyX. Please read the bug-reporting instructions
in Help-Introduction and
Jean-Marc Lasgouttes wrote:
Could bug 2549 on OS X
http://bugzilla.lyx.org/show_bug.cgi?id=2549
be related to this?
I think so. Changing app to a pointer also in qt3 gets also rid of the
famous mutex destroy failure message.
I think we need to change both qt3 and qt4 in such a way that the
Georg Baum wrote:
Jean-Marc Lasgouttes wrote:
Could bug 2549 on OS X
http://bugzilla.lyx.org/show_bug.cgi?id=2549
be related to this?
I think so. Changing app to a pointer also in qt3 gets also rid of the
famous mutex destroy failure message.
I think we need to change both qt3 and qt4 in
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Jean-Marc Lasgouttes wrote:
Could bug 2549 on OS X http://bugzilla.lyx.org/show_bug.cgi?id=2549
be related to this?
Georg I think so. Changing app to a pointer also in qt3 gets also rid
Georg of the famous mutex destroy failure message.
Abdelrazak Younes wrote:
> Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
Georg
Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
You're right, I'll do that. This reminds me of some feature requests for
SVN:
1) in lyx.cvs list, put an
Georg Baum wrote:
Abdelrazak Younes wrote:
Will commit now.
It would be nice if you could add the comment from your commit log to the .C
file. Otherwise it is easy to get forgotten.
Done.
Abdel.
Index: lyx_gui.C
===
---
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
>> When lyx-qt4 ends, I get: lyx: SIGSEGV signal caught Sorry, you
>> have found a bug in LyX. Please read the bug-reporting instructions
>> in Help->Introduction and send us a bug
Jean-Marc Lasgouttes wrote:
"Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get: lyx: SIGSEGV signal caught Sorry, you
have found a bug in LyX. Please read the bug-reporting instructions
in Help->Introduction
Jean-Marc Lasgouttes wrote:
> Could bug 2549 on OS X
> http://bugzilla.lyx.org/show_bug.cgi?id=2549
> be related to this?
I think so. Changing app to a pointer also in qt3 gets also rid of the
famous "mutex destroy failure" message.
I think we need to change both qt3 and qt4 in such a way that
Georg Baum wrote:
Jean-Marc Lasgouttes wrote:
Could bug 2549 on OS X
http://bugzilla.lyx.org/show_bug.cgi?id=2549
be related to this?
I think so. Changing app to a pointer also in qt3 gets also rid of the
famous "mutex destroy failure" message.
I think we need to change both qt3 and qt4 in
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> Could bug 2549 on OS X http://bugzilla.lyx.org/show_bug.cgi?id=2549
>> be related to this?
Georg> I think so. Changing app to a pointer also in qt3 gets also rid
Georg> of the famous "mutex destroy
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is automatic
when quitting. But you are probably right. Will commit soon.
atm lyx hangs when closing the app (qt4, windows)
something to
Edwin Leuven wrote:
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is
automatic when quitting. But you are probably right. Will commit soon.
atm lyx hangs when closing the app (qt4,
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is
automatic when quitting. But you are probably right. Will commit soon.
atm lyx hangs
Am Sonntag, 28. Mai 2006 17:01 schrieb Abdelrazak Younes:
Abdelrazak Younes wrote:
Edwin Leuven wrote:
atm lyx hangs when closing the app (qt4, windows)
something to do with this?
Maybe... Just to be sure, try to comment out line 284 in lyx_gui.C:
No, it's not that but something
Georg Baum wrote:
This backtrace does not match Edwins report: atm lyx hangs when closing
the app. That implies that he could run it before, and that means that
parse_init() has been executed already. I would be very surprised if this
problem has nothing to do with the qApp change.
Edwin,
Georg Baum wrote:
Am Sonntag, 28. Mai 2006 17:01 schrieb Abdelrazak Younes:
Abdelrazak Younes wrote:
Edwin Leuven wrote:
atm lyx hangs when closing the app (qt4, windows)
something to do with this?
Maybe... Just to be sure, try to comment out line 284 in lyx_gui.C:
No, it's not that but
Abdelrazak Younes wrote:
...
I recompiling in debug mode to see where it crash precisely in parse_init.
And of course the full debug version makes mingw gdb crash... I have to
install cygwin.
Will report later.
Abdel.
Abdelrazak Younes wrote:
Georg Baum wrote:
This backtrace does not match Edwins report: atm lyx hangs when
closing the app. That implies that he could run it before, and that
means that parse_init() has been executed already. I would be very
surprised if this problem has nothing to do with
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
This backtrace does not match Edwins report: atm lyx hangs when
closing the app. That implies that he could run it before, and that
means that parse_init() has been executed already. I would be very
surprised if this problem
Abdelrazak Younes wrote:
Reverting to a static QApplication solves the problem. I guess we have
an incompatibility problem between linux and windows!
I think that encapsulating this init code inside a class and make the
QApplication a member of this class should solve the problem.
OK, until
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is automatic
when quitting. But you are probably right. Will commit soon.
atm lyx hangs when closing the app (qt4, windows)
something to
Edwin Leuven wrote:
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is
automatic when quitting. But you are probably right. Will commit soon.
atm lyx hangs when closing the app (qt4,
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
I was maybe a misleaded by the name of the function (start). There is
one QApplication per application so I guess the destruction is
automatic when quitting. But you are probably right. Will commit soon.
atm lyx hangs
Am Sonntag, 28. Mai 2006 17:01 schrieb Abdelrazak Younes:
> Abdelrazak Younes wrote:
> > Edwin Leuven wrote:
> >> atm lyx hangs when closing the app (qt4, windows)
> >>
> >> something to do with this?
> >
> > Maybe... Just to be sure, try to comment out line 284 in lyx_gui.C:
>
> No, it's not
Georg Baum wrote:
This backtrace does not match Edwins report: "atm lyx hangs when closing
the app". That implies that he could run it before, and that means that
parse_init() has been executed already. I would be very surprised if this
problem has nothing to do with the qApp change.
Edwin,
Georg Baum wrote:
Am Sonntag, 28. Mai 2006 17:01 schrieb Abdelrazak Younes:
Abdelrazak Younes wrote:
Edwin Leuven wrote:
atm lyx hangs when closing the app (qt4, windows)
something to do with this?
Maybe... Just to be sure, try to comment out line 284 in lyx_gui.C:
No, it's not that but
Abdelrazak Younes wrote:
...
I recompiling in debug mode to see where it crash precisely in parse_init.
And of course the full debug version makes mingw gdb crash... I have to
install cygwin.
Will report later.
Abdel.
Abdelrazak Younes wrote:
Georg Baum wrote:
This backtrace does not match Edwins report: "atm lyx hangs when
closing the app". That implies that he could run it before, and that
means that parse_init() has been executed already. I would be very
surprised if this problem has nothing to do with
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
This backtrace does not match Edwins report: "atm lyx hangs when
closing the app". That implies that he could run it before, and that
means that parse_init() has been executed already. I would be very
surprised if this
Abdelrazak Younes wrote:
Reverting to a static QApplication solves the problem. I guess we have
an incompatibility problem between linux and windows!
I think that encapsulating this init code inside a class and make the
QApplication a member of this class should solve the problem.
OK, until
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get:
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting
instructions in Help-Introduction and send us a bug report, if
necessary. Thanks !
Bye.
Avbrutt (SIGABRT)
And no
Georg Baum wrote:
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get:
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting
instructions in Help-Introduction and send us a bug report, if
necessary. Thanks !
Bye.
Avbrutt
Georg Baum wrote:
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
Abdel, do you have any idea why this happens?
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor. I
am not sure this will solve
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor. I
am not sure this will solve the crash but your backtrace seems to imply
so. If not, I
Am Samstag, 27. Mai 2006 14:57 schrieb Abdelrazak Younes:
I have maybe an idea. Peter Kummel claims the following in his Cmake
patch:
---
and this fixes the crash on exit under windows, maybe
Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor. I
am not sure this will solve the crash but your backtrace seems to imply
Georg Baum wrote:
Am Samstag, 27. Mai 2006 14:57 schrieb Abdelrazak Younes:
I have maybe an idea. Peter Kummel claims the following in his Cmake
patch:
---
and this fixes the crash on exit under windows, maybe
Am Samstag, 27. Mai 2006 15:40 schrieb Abdelrazak Younes:
OK, then this patch use a straight QApplication. QLApplication is used
only for Mac as far as I see. And use qApp only.
Does not help:
#0 0xb7b94bcc in QPixmapCache::clear () from /usr/lib/libQtGui.so.4
#1 0xb7b4ddb5 in
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor.
This was the right idea. The 'static' LQApplication changed the
destruction order in a way qt
Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor.
This was the right idea. The 'static' LQApplication changed the
Georg Baum wrote:
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor.
This was the right idea. The 'static' LQApplication changed the
Am Samstag, 27. Mai 2006 17:11 schrieb Abdelrazak Younes:
Georg Baum wrote:
+ delete app;
Is this necessary?
I think so. It makes sure that the LQApplication object is destructed at a
defined time. How should the compiler know when to destruct it otherwise?
Georg
Georg Baum wrote:
Am Samstag, 27. Mai 2006 17:11 schrieb Abdelrazak Younes:
Georg Baum wrote:
+ delete app;
Is this necessary?
I think so. It makes sure that the LQApplication object is destructed at a
defined time. How should the compiler know when to destruct it otherwise?
I was
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
> When lyx-qt4 ends, I get:
> lyx: SIGSEGV signal caught
> Sorry, you have found a bug in LyX. Please read the bug-reporting
> instructions in Help->Introduction and send us a bug report, if
> necessary. Thanks !
> Bye.
> Avbrutt (SIGABRT)
>
Georg Baum wrote:
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
When lyx-qt4 ends, I get:
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting
instructions in Help->Introduction and send us a bug report, if
necessary. Thanks !
Bye.
Avbrutt
Georg Baum wrote:
Am Freitag, 26. Mai 2006 11:33 schrieb Helge Hafting:
Abdel, do you have any idea why this happens?
Another idea... Maybe the QApplication destruction is happening too soon
in the exit process, this patch remove the QLApplication destructor. I
am not sure this will solve
Am Samstag, 27. Mai 2006 15:20 schrieb Abdelrazak Younes:
> Another idea... Maybe the QApplication destruction is happening too soon
> in the exit process, this patch remove the QLApplication destructor. I
> am not sure this will solve the crash but your backtrace seems to imply
> so. If not, I
Am Samstag, 27. Mai 2006 14:57 schrieb Abdelrazak Younes:
> I have maybe an idea. Peter Kummel claims the following in his Cmake
patch:
>
> ---
> and this fixes the crash on exit under windows, maybe
>
1 - 100 of 110 matches
Mail list logo
