Fwd: Re: crash

2014-09-22 Thread Jürgen Spitzmüller 

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre pdu...@gmx.com
An: Jürgen Spitzmüller sp...@lyx.org

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Monday, September 22, 2014 at 5:45 PM
 From: Jürgen Spitzmüller sp...@lyx.org
 To: lyx-users@lists.lyx.org
 Subject: Re: crash

 Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
  Hello,
  
  I still have this continuous issue that if I have a first document
  .lyx file open and that I want to open another complex lyx file.
  It just crashes!
  
  SIGSEGV signal caught!
  
  It starting to really bother me!
 
 In order to help, we need more information:
 
 * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
 * an example document
 
 Did you already file a bug report for this? If so, what is the ticket number? 
 If not, please do and provide all necessary information there.
 
 Thanks,
 Jürgen
 
 

-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-redhat-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib64/libthread_db.so.1.
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching after fork from child process 15759.
Detaching after fork from child process 15760.
Detaching after fork from child process 15761.
Detaching after fork from child process 15762.
Detaching after fork from child process 15763.
Detaching after fork from child process 15764.
Detaching after fork

Fwd: Re: crash

2014-09-22 Thread Jürgen Spitzmüller 

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre pdu...@gmx.com
An: Jürgen Spitzmüller sp...@lyx.org

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Monday, September 22, 2014 at 5:45 PM
 From: Jürgen Spitzmüller sp...@lyx.org
 To: lyx-users@lists.lyx.org
 Subject: Re: crash

 Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
  Hello,
  
  I still have this continuous issue that if I have a first document
  .lyx file open and that I want to open another complex lyx file.
  It just crashes!
  
  SIGSEGV signal caught!
  
  It starting to really bother me!
 
 In order to help, we need more information:
 
 * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
 * an example document
 
 Did you already file a bug report for this? If so, what is the ticket number? 
 If not, please do and provide all necessary information there.
 
 Thanks,
 Jürgen
 
 

-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-redhat-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib64/libthread_db.so.1.
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching after fork from child process 15759.
Detaching after fork from child process 15760.
Detaching after fork from child process 15761.
Detaching after fork from child process 15762.
Detaching after fork from child process 15763.
Detaching after fork from child process 15764.
Detaching after fork

Fwd: Re: crash

2014-09-22 Thread Jürgen Spitzmüller 

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre 
An: Jürgen Spitzmüller 

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Monday, September 22, 2014 at 5:45 PM
> From: "Jürgen Spitzmüller" 
> To: lyx-users@lists.lyx.org
> Subject: Re: crash
>
> Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
> > Hello,
> > 
> > I still have this continuous issue that if I have a first document
> > .lyx file open and that I want to open another "complex" lyx file.
> > It just crashes!
> > 
> > SIGSEGV signal caught!
> > 
> > It starting to really bother me!
> 
> In order to help, we need more information:
> 
> * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
> * an example document
> 
> Did you already file a bug report for this? If so, what is the ticket number? 
> If not, please do and provide all necessary information there.
> 
> Thanks,
> Jürgen
> 
> 
>
-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching after fork from child process 15759.
Detaching after fork from child process 15760.
Detaching after fork from child process 15761.
Detaching after fork from child process 15762.
Detaching after fork from child process 15763.
Detaching after