Am 26.04.2019 um 10:28 schrieb jezZiFeR <jezzi...@gmail.com>: > > Dear Stephan, > > hm, now I have got a SIGSEV-signal again and could reproduce it every time I > use the dialogue with »export as«, like this: > > file–export–export as > > I get the message, that there are no information to export to the chosen > format: > »Keine Informationen vorhanden, um das Format HTML zu exportieren.« > and the SIGSEV-error-message. So this time I could send the stack trace, see > below.
Dear Jess, thank you for it. Of course it looks like garbage for mere mortal people. If I try to interpret it I can see in line (6) our code is involved the last time before the crash. Here the method named lyx::frontend::Action::action is called and this method does nearly nothing except calling some configured method indirectly. A crash here means the internal memory structures of the running LyX got corrupted at some point in time before. Unfortunately these things happen unnoticed at the time the code to blame is executed. Probably there is some memory passed back to the OS too early. So, I don’t have a solution for this crash. But it’s almost sure it’s unrelated with the availability of the export function. Best regards, Stephan > > Thanks in advance, all best > Jess > > > > — > > ( 1) 1 lyx 0x000000010560d5d6 > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b > : 1 lyx 0x000000010560d5d6 > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b > + 199 > ( 2) 2 lyx 0x000000010560d9e1 > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b > : 2 lyx 0x000000010560d9e1 > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b > + 135 > ( 3) 3 lyx 0x00000001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx > 0x00000001053a71ce _ZN3lyxL13error_handlerEi + 603 > ( 4) 4 libsystem_platform.dylib 0x00007fff5d488b3d _sigtramp : 4 > libsystem_platform.dylib 0x00007fff5d488b3d _sigtramp + 29 > ( 5) 5 libsystem_malloc.dylib 0x00007fff5d44c807 malloc_zone_malloc : 5 > libsystem_malloc.dylib 0x00007fff5d44c807 malloc_zone_malloc + 103 > ( 6) 6 lyx 0x00000001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx > 0x00000001055f60aa _ZN3lyx8frontend6Action6actionEv + 74 > ( 7) 7 QtCore 0x0000000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 7 > QtCore 0x0000000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > ( 8) 8 QtWidgets 0x0000000106bce457 _ZN7QAction8activateENS_11ActionEventE : > 8 QtWidgets 0x0000000106bce457 _ZN7QAction8activateENS_11ActionEventE + 263 > ( 9) 9 QtCore 0x0000000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 9 > QtCore 0x0000000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > ( 10) 10 QtCore 0x0000000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore > 0x0000000106781ac1 _ZN7QObject5eventEP6QEvent + 801 > ( 11) 11 QtWidgets 0x0000000106bd7dfd > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets > 0x0000000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > + 301 > ( 12) 12 QtWidgets 0x0000000106bd9177 > _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 0x0000000106bd9177 > _ZN12QApplication6notifyEP7QObjectP6QEvent + 391 > ( 13) 13 lyx 0x000000010561cb6b > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx > 0x000000010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent > + 21 > ( 14) 14 QtCore 0x0000000106757be4 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore > 0x0000000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + > 164 > ( 15) 15 QtCore 0x0000000106758d6b > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 15 > QtCore 0x0000000106758d6b > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 891 > ( 16) 16 libqcocoa.dylib 0x000000010926010e > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 libqcocoa.dylib > 0x000000010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + > 190 > ( 17) 17 libqcocoa.dylib 0x00000001092609d1 > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 > libqcocoa.dylib 0x00000001092609d1 > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33 > ( 18) 18 CoreFoundation 0x00007fff3006d395 > __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ : 18 > CoreFoundation 0x00007fff3006d395 > __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 > ( 19) 19 CoreFoundation 0x00007fff3006d33b __CFRunLoopDoSource0 : 19 > CoreFoundation 0x00007fff3006d33b __CFRunLoopDoSource0 + 108 > ( 20) 20 CoreFoundation 0x00007fff30050dd1 __CFRunLoopDoSources0 : 20 > CoreFoundation 0x00007fff30050dd1 __CFRunLoopDoSources0 + 195 > ( 21) 21 CoreFoundation 0x00007fff3005037a __CFRunLoopRun : 21 CoreFoundation > 0x00007fff3005037a __CFRunLoopRun + 1219 > ( 22) 22 CoreFoundation 0x00007fff3004fc64 CFRunLoopRunSpecific : 22 > CoreFoundation 0x00007fff3004fc64 CFRunLoopRunSpecific + 463 > ( 23) 23 HIToolbox 0x00007fff2f2e6ab5 RunCurrentEventLoopInMode : 23 > HIToolbox 0x00007fff2f2e6ab5 RunCurrentEventLoopInMode + 293 > ( 24) 24 HIToolbox 0x00007fff2f2e66f4 ReceiveNextEventCommon : 24 HIToolbox > 0x00007fff2f2e66f4 ReceiveNextEventCommon + 371 > ( 25) 25 HIToolbox 0x00007fff2f2e6568 > _BlockUntilNextEventMatchingListInModeWithFilter : 25 HIToolbox > 0x00007fff2f2e6568 _BlockUntilNextEventMatchingListInModeWithFilter + 64 > ( 26) 26 AppKit 0x00007fff2d5a1363 _DPSNextEvent : 26 AppKit > 0x00007fff2d5a1363 _DPSNextEvent + 997 > ( 27) 27 AppKit 0x00007fff2d5a0102 -[NSApplication: 27 AppKit > 0x00007fff2d5a0102 -[NSApplication(NSEvent) > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 > ( 28) 28 AppKit 0x00007fff2d59a165 -[NSApplication run] : 28 AppKit > 0x00007fff2d59a165 -[NSApplication run] + 699 > ( 29) 29 libqcocoa.dylib 0x000000010925f73d > _ZN21QCocoaEventDispatcher13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > : 29 libqcocoa.dylib 0x000000010925f73d > _ZN21QCocoaEventDispatcher13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > + 2445 > ( 30) 30 QtCore 0x00000001067536e1 > _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE : 30 QtCore > 0x00000001067536e1 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 417 > ( 31) 31 QtCore 0x0000000106758288 _ZN16QCoreApplication4execEv : 31 QtCore > 0x0000000106758288 _ZN16QCoreApplication4execEv + 392 > ( 32) 32 lyx 0x00000001053a2841 _ZN3lyx3LyX4execERiPPc : 32 lyx > 0x00000001053a2841 _ZN3lyx3LyX4execERiPPc + 1009 > ( 33) 33 lyx 0x0000000105284d1f main : 33 lyx 0x0000000105284d1f main + 79 > ( 34) 34 libdyld.dylib 0x00007fff5d29ded9 start : 34 libdyld.dylib > 0x00007fff5d29ded9 start + 1 > > > > Am 25. Apr. 2019, 22:50 +0200 schrieb Stephan Witt <st.w...@gmx.net>: >> Am 25.04.2019 um 22:14 schrieb jezZiFeR <jezzi...@gmail.com>: >>> >>> Dear Stephan, >>> >>> with the tutorial it seems that I also do not get a SIGSEV in some cases, >>> but I also get it when I go via: >>> file–export–export as… >>> >>> When I tried this for.html I also got this message: »Kann keinen >>> LaTeX-Befehl für das Zeichen '⌃' (Code-Punkt 0x2303) finden. >>> Einige Zeichen Ihres Dokuments sind mit der gewählten Kodierung >>> wahrscheinlich nicht darstellbar. >>> Eine Änderung der Dokumentkodierung auf 'utf8' könnte helfen.« >>> >>> This means something like the is no LaTeX-command for »^« and it is >>> suggested to change the document’s coding to utf 8, which is not possible >>> for the tutorial-file. >> >> Yes, this is a problem with the tutorial in LyX 2.3.2 and will be fixed in >> 2.3.3. >> >>> >>> Maybe it is interesting, that the dialogue of two different documents (mine >>> & German tutorial) produce different export-possibilities and the tutorial >>> has much more. I add two screenshots to make it clearer. >> >> Hmmm, the export possibilities efficiently depend on the existing >> converters. The longer list doesn’t necessarily mean more possibilities… I >> don’t know off-hand how the lists are constructed and why they contain >> useless entries. >> >>> >>> Excuse me, what is the »sack trace«? Should I send you the details of the >>> SIGSEV? >> >> Yes, please. >> >> Best regards, >> Stephan >> >>> I will continue trying some more documents tomorrow. >>> >>> Thank you, all best >>> Jess >>> >>> >>> >>> >>> >>> >>> >>> Am 25. Apr. 2019, 21:52 +0200 schrieb Stephan Witt <st.w...@gmx.net>: >>>> Am 25.04.2019 um 18:56 schrieb jezZiFeR <jezzi...@gmail.com>: >>>>> >>>>> Hello, >>>>> >>>>> I try to export ePubs for a while now and it never worked in different >>>>> configurations. LyX was always freezing. In the moment I use OS 10.14.3, >>>>> Intel and LyX 2.3.2 with TeXLive 2018. >>>>> >>>>> When I do the following: >>>>> + file – export as – DocBook (XML) and then try to save I get the >>>>> follwing error: >>>>> »Keine Informationen vorhanden, um das Format DocBook (XML) zu >>>>> exportieren.« >>>>> In English this means something like »There is no information to export >>>>> the format DocBook (XML). >>>>> + Now I click »cancel« and get a SIGSEV-signal, like every time. >>>>> >>>>> Does anybody have a hint what I could do? Would be very good to use XML, >>>>> maybe there is a workaround. >>>>> >>>>> Thanks, all best >>>>> Jess >>>> >>>> Hello Jess, >>>> >>>> I’m on Mac OS 10.14.4 with LyX 2.3.2. I’m unable to export to DocBook too. >>>> But - at least with the Tutorial - I don’t get a crash on Cancel. >>>> >>>> Can you send me the stack trace please and tell me if it happens with >>>> every LyX document or with some of your documents only? >>>> >>>> Best regards, >>>> Stephan >>> <Bildschirmfoto 2019-04-25 um 22.04.41.png><Bildschirmfoto 2019-04-25 um >>> 22.04.20.png> >>
