Re: SIGSEGV error

2017-07-26 Thread Scott Kostyshak
On Tue, Jul 25, 2017 at 01:43:15PM -0700, Christos Makridis wrote:
> Hey Scott,
> 
> I actually don't have the file now since I overwrote it after fixing the
> problem, but I think you could replicate it by putting in a "bad" character
> and trying to paste it into lyx and then pdf it? I am not really sure what
> constitutes a bad character in lyx versus something that is okay in word.

I've tried that and can't reproduce. The characters don't often show up
correctly, but I never get a SIGSEGV.

Scott


Re: SIGSEGV error

2017-07-25 Thread Christos Makridis
Hey Scott,

I actually don't have the file now since I overwrote it after fixing the
problem, but I think you could replicate it by putting in a "bad" character
and trying to paste it into lyx and then pdf it? I am not really sure what
constitutes a bad character in lyx versus something that is okay in word.


Re: SIGSEGV error

2017-07-25 Thread Scott Kostyshak
On Wed, Jun 21, 2017 at 10:58:36PM +0200, Jean-Marc Lasgouttes wrote:
> Le 21/06/17 à 22:21, Christos Makridis a écrit :
> > Perfect, looking at the source pane helped diagnose the problem -- an
> > imbalanced space from MS word -- great suggestion! I did not know that
> > source pane even existed before.
> > 
> > (I would have added more details, like an example, but I wasn't sure
> > what could be causing it before. I am using the latest version of lyx on
> > a windows machine FYI.)
> > 
> > Thank you for teaching me this new trick!
> 
> I am happy for you, obviously, but nevertheless LyX should not crash in this
> situation. Can you send us an example file that exhibits the problem?

Christos, do you have an example file that you can send us?

Thanks,

Scott


Re: SIGSEGV error

2017-06-21 Thread Jean-Marc Lasgouttes

Le 21/06/17 à 22:21, Christos Makridis a écrit :

Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.

(I would have added more details, like an example, but I wasn't sure
what could be causing it before. I am using the latest version of lyx on
a windows machine FYI.)

Thank you for teaching me this new trick!


I am happy for you, obviously, but nevertheless LyX should not crash in 
this situation. Can you send us an example file that exhibits the problem?


JMarc


Re: SIGSEGV error

2017-06-21 Thread Christos Makridis
Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.

(I would have added more details, like an example, but I wasn't sure what
could be causing it before. I am using the latest version of lyx on a
windows machine FYI.)

Thank you for teaching me this new trick!


Re: SIGSEGV error

2017-06-21 Thread Paul A. Rubin

On 06/21/2017 03:42 PM, Christos Makridis wrote:

Hey everyone,

I've googled around and there doesn't seem to be a consensus about the 
source of the problem -- some just suggest making sure the lyx is the 
latest version.


I've attached the error as a screen shot. But, the problem seems to be 
rooted in some text that I copy/pasted from a word doc. The formatting 
was different, so I first pasted into another word doc with no special 
formatting, and then into lyx. But when I try to pdf the document, it 
crashes. (Before, it would crash when I highlighted the pasted in 
text.) It seems to be "normal" now that I took that part of the text out.


Any ideas what is going wrong?

--
Christos Makridis
Ph.D. Candidate, Stanford University
Department of Management Science & Engineering
Department of Economics
www.christosmakridis.com 
A first thought is to look at the LyX document the document with the 
offending text pasted in, and use View > Source Pane to get a look at 
what the source text going to LaTeX looks like. That might let you spot 
some character that looks harmless in the GUI (and in Word) but actually 
is the Unicode character for the apocalypse or something.


Failing that, could you post a minimal example that contains just enough 
text to cause LyX to blow up at your end?


Also, it might help to know what operating system you use, what LaTeX 
system (TeXLive, MikTeX, ...) and what version/build of LyX (Help > 
About LyX).


Cheers,
Paul



Re: SIGSEGV Error in Mavericks

2014-12-08 Thread Julio Rojas
I believe this is the log entry associated with this error:

Process: lyx [4296]
Path:/Applications/LyX.app/Contents/MacOS/./lyx
Identifier:  org.lyx.lyx
Version: 2.1.2.2 (???)
Code Type:   X86-64 (Native)
Parent Process:  bash [4204]
Responsible: Terminal [4201]
User ID: 501

Date/Time:   2014-12-08 11:29:51.990 -0300
OS Version:  Mac OS X 10.9.5 (13F34)
Report Version:  11
Anonymous UUID:  22AA66AB-FA38-07FF-0138-190637EE210E

Sleep/Wake UUID: F52DD08B-0A10-4873-89B7-B7BA7B05E4FC

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0010

VM Regions Near 0x10:
--
__TEXT 0001-0001008e1000 [ 9092K]
r-x/rwx SM=COW  /Applications/LyX.app/Contents/MacOS/lyx

Application Specific Information:
abort() called
*** error for object 0x10380d738: pointer being freed was not allocated


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fff8b56b866 __pthread_kill + 10
1   libsystem_pthread.dylib   0x7fff8e50635c pthread_kill + 92
2   libsystem_c.dylib 0x7fff8bf73b1a abort + 125
3   libsystem_malloc.dylib 0x7fff85af807f free + 411
4   QtGui 0x00010128ea10 cleanup_mimes() + 112
5   QtCore 0x000101003f05
qt_call_post_routines() + 101
6   QtGui 0x0001012354a7
QApplication::~QApplication() + 105
7   org.lyx.lyx   0x0001002eb78a 0x1 + 3061642
8   org.lyx.lyx   0x0001002ea71e 0x1 + 3057438
9   org.lyx.lyx   0x0001002ea52f 0x1 + 3056943
10  org.lyx.lyx   0x0001000ec9e4 0x1 + 969188
11  libsystem_platform.dylib   0x7fff88d5f5aa _sigtramp + 26
12  libobjc.A.dylib   0x7fff8814d62a (anonymous
namespace)::AutoreleasePoolPage::pop(void*) + 454
13  com.apple.CoreFoundation   0x7fff89feb932 _CFAutoreleasePoolPop
+ 50
14  com.apple.Foundation   0x7fff923c354c -[NSAutoreleasePool
release] + 140
15  org.lyx.lyx   0x0001004edc8b 0x1 + 5168267
16  org.lyx.lyx   0x0001002f343e 0x1 + 3093566
17  org.lyx.lyx   0x0001000ede9d 0x1 + 974493
18  org.lyx.lyx   0x0001000f0fe0 0x1 + 987104
19  org.lyx.lyx   0x00011cc2 0x1 + 7362
20  org.lyx.lyx   0x00011c74 0x1 + 7284

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib 0x7fff8b56c662 kevent64 + 10
1   libdispatch.dylib 0x7fff8eb66421 _dispatch_mgr_invoke +
239
2   libdispatch.dylib 0x7fff8eb66136 _dispatch_mgr_thread +
52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib 0x7fff8b56b9aa __select + 10

I hope this helps. Regards,

-
Julio Rojas
jcredbe...@gmail.com

On Mon, Dec 8, 2014 at 11:32 AM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

 While closing Lyx 2.1.2.2 in Mavericks the following error appeared:

 ¡Señal SIGSEGV capturada!

 Lo sentimos, has encontrado un fallo en LyX, ojalá no hayas perdido datos.

 Por favor, lee las instrucciones sobre informe de fallos en
 'AyudaIntroducción' y envíanoslo, si es necesario. ¡Gracias!

 Adiós.

 2014-12-08 11:29:51.974 lyx[4296:507] modalSession has been exited
 prematurely - check for a reentrant call to endModalSession:

 lyx(4296,0x7fff768b7310) malloc: *** error for object 0x10380d738: pointer
 being freed was not allocated

 *** set a breakpoint in malloc_error_break to debug

 Abort trap: 6

 Any idea?

 Regards,
 -
 Julio Rojas
 jcredbe...@gmail.com



Re: SIGSEGV Error in Mavericks

2014-12-08 Thread Julio Rojas
I believe this is the log entry associated with this error:

Process: lyx [4296]
Path:/Applications/LyX.app/Contents/MacOS/./lyx
Identifier:  org.lyx.lyx
Version: 2.1.2.2 (???)
Code Type:   X86-64 (Native)
Parent Process:  bash [4204]
Responsible: Terminal [4201]
User ID: 501

Date/Time:   2014-12-08 11:29:51.990 -0300
OS Version:  Mac OS X 10.9.5 (13F34)
Report Version:  11
Anonymous UUID:  22AA66AB-FA38-07FF-0138-190637EE210E

Sleep/Wake UUID: F52DD08B-0A10-4873-89B7-B7BA7B05E4FC

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0010

VM Regions Near 0x10:
--
__TEXT 0001-0001008e1000 [ 9092K]
r-x/rwx SM=COW  /Applications/LyX.app/Contents/MacOS/lyx

Application Specific Information:
abort() called
*** error for object 0x10380d738: pointer being freed was not allocated


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fff8b56b866 __pthread_kill + 10
1   libsystem_pthread.dylib   0x7fff8e50635c pthread_kill + 92
2   libsystem_c.dylib 0x7fff8bf73b1a abort + 125
3   libsystem_malloc.dylib 0x7fff85af807f free + 411
4   QtGui 0x00010128ea10 cleanup_mimes() + 112
5   QtCore 0x000101003f05
qt_call_post_routines() + 101
6   QtGui 0x0001012354a7
QApplication::~QApplication() + 105
7   org.lyx.lyx   0x0001002eb78a 0x1 + 3061642
8   org.lyx.lyx   0x0001002ea71e 0x1 + 3057438
9   org.lyx.lyx   0x0001002ea52f 0x1 + 3056943
10  org.lyx.lyx   0x0001000ec9e4 0x1 + 969188
11  libsystem_platform.dylib   0x7fff88d5f5aa _sigtramp + 26
12  libobjc.A.dylib   0x7fff8814d62a (anonymous
namespace)::AutoreleasePoolPage::pop(void*) + 454
13  com.apple.CoreFoundation   0x7fff89feb932 _CFAutoreleasePoolPop
+ 50
14  com.apple.Foundation   0x7fff923c354c -[NSAutoreleasePool
release] + 140
15  org.lyx.lyx   0x0001004edc8b 0x1 + 5168267
16  org.lyx.lyx   0x0001002f343e 0x1 + 3093566
17  org.lyx.lyx   0x0001000ede9d 0x1 + 974493
18  org.lyx.lyx   0x0001000f0fe0 0x1 + 987104
19  org.lyx.lyx   0x00011cc2 0x1 + 7362
20  org.lyx.lyx   0x00011c74 0x1 + 7284

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib 0x7fff8b56c662 kevent64 + 10
1   libdispatch.dylib 0x7fff8eb66421 _dispatch_mgr_invoke +
239
2   libdispatch.dylib 0x7fff8eb66136 _dispatch_mgr_thread +
52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib 0x7fff8b56b9aa __select + 10

I hope this helps. Regards,

-
Julio Rojas
jcredbe...@gmail.com

On Mon, Dec 8, 2014 at 11:32 AM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

 While closing Lyx 2.1.2.2 in Mavericks the following error appeared:

 ¡Señal SIGSEGV capturada!

 Lo sentimos, has encontrado un fallo en LyX, ojalá no hayas perdido datos.

 Por favor, lee las instrucciones sobre informe de fallos en
 'AyudaIntroducción' y envíanoslo, si es necesario. ¡Gracias!

 Adiós.

 2014-12-08 11:29:51.974 lyx[4296:507] modalSession has been exited
 prematurely - check for a reentrant call to endModalSession:

 lyx(4296,0x7fff768b7310) malloc: *** error for object 0x10380d738: pointer
 being freed was not allocated

 *** set a breakpoint in malloc_error_break to debug

 Abort trap: 6

 Any idea?

 Regards,
 -
 Julio Rojas
 jcredbe...@gmail.com



Re: SIGSEGV Error in Mavericks

2014-12-08 Thread Julio Rojas
I believe this is the log entry associated with this error:

Process: lyx [4296]
Path:/Applications/LyX.app/Contents/MacOS/./lyx
Identifier:  org.lyx.lyx
Version: 2.1.2.2 (???)
Code Type:   X86-64 (Native)
Parent Process:  bash [4204]
Responsible: Terminal [4201]
User ID: 501

Date/Time:   2014-12-08 11:29:51.990 -0300
OS Version:  Mac OS X 10.9.5 (13F34)
Report Version:  11
Anonymous UUID:  22AA66AB-FA38-07FF-0138-190637EE210E

Sleep/Wake UUID: F52DD08B-0A10-4873-89B7-B7BA7B05E4FC

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0010

VM Regions Near 0x10:
-->
__TEXT 0001-0001008e1000 [ 9092K]
r-x/rwx SM=COW  /Applications/LyX.app/Contents/MacOS/lyx

Application Specific Information:
abort() called
*** error for object 0x10380d738: pointer being freed was not allocated


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fff8b56b866 __pthread_kill + 10
1   libsystem_pthread.dylib   0x7fff8e50635c pthread_kill + 92
2   libsystem_c.dylib 0x7fff8bf73b1a abort + 125
3   libsystem_malloc.dylib 0x7fff85af807f free + 411
4   QtGui 0x00010128ea10 cleanup_mimes() + 112
5   QtCore 0x000101003f05
qt_call_post_routines() + 101
6   QtGui 0x0001012354a7
QApplication::~QApplication() + 105
7   org.lyx.lyx   0x0001002eb78a 0x1 + 3061642
8   org.lyx.lyx   0x0001002ea71e 0x1 + 3057438
9   org.lyx.lyx   0x0001002ea52f 0x1 + 3056943
10  org.lyx.lyx   0x0001000ec9e4 0x1 + 969188
11  libsystem_platform.dylib   0x7fff88d5f5aa _sigtramp + 26
12  libobjc.A.dylib   0x7fff8814d62a (anonymous
namespace)::AutoreleasePoolPage::pop(void*) + 454
13  com.apple.CoreFoundation   0x7fff89feb932 _CFAutoreleasePoolPop
+ 50
14  com.apple.Foundation   0x7fff923c354c -[NSAutoreleasePool
release] + 140
15  org.lyx.lyx   0x0001004edc8b 0x1 + 5168267
16  org.lyx.lyx   0x0001002f343e 0x1 + 3093566
17  org.lyx.lyx   0x0001000ede9d 0x1 + 974493
18  org.lyx.lyx   0x0001000f0fe0 0x1 + 987104
19  org.lyx.lyx   0x00011cc2 0x1 + 7362
20  org.lyx.lyx   0x00011c74 0x1 + 7284

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib 0x7fff8b56c662 kevent64 + 10
1   libdispatch.dylib 0x7fff8eb66421 _dispatch_mgr_invoke +
239
2   libdispatch.dylib 0x7fff8eb66136 _dispatch_mgr_thread +
52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib 0x7fff8b56b9aa __select + 10

I hope this helps. Regards,

-
Julio Rojas
jcredbe...@gmail.com

On Mon, Dec 8, 2014 at 11:32 AM, Julio Rojas  wrote:

> Dear all,
>
> While closing Lyx 2.1.2.2 in Mavericks the following error appeared:
>
> ¡Señal SIGSEGV capturada!
>
> Lo sentimos, has encontrado un fallo en LyX, ojalá no hayas perdido datos.
>
> Por favor, lee las instrucciones sobre informe de fallos en
> 'Ayuda>Introducción' y envíanoslo, si es necesario. ¡Gracias!
>
> Adiós.
>
> 2014-12-08 11:29:51.974 lyx[4296:507] modalSession has been exited
> prematurely - check for a reentrant call to endModalSession:
>
> lyx(4296,0x7fff768b7310) malloc: *** error for object 0x10380d738: pointer
> being freed was not allocated
>
> *** set a breakpoint in malloc_error_break to debug
>
> Abort trap: 6
>
> Any idea?
>
> Regards,
> -
> Julio Rojas
> jcredbe...@gmail.com
>