bugGNU TeXmacs - Bugs: bug #48441, TeXmacs 1.99.4 segfault

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #48441: TeXmacs 1.99.4 segfault

Submitter:  Peter Rapcan <peterrapcan>
Submitted:  Thu 07 Jul 2016 07:40:38 PM UTC
   
 
Category:  Qt port Priority:  5 - Normal
Item Group:  Error Status:  Need Info
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Closed
Release:  None Release:  version1550
Fixed Release:  None Fixed Release: 
Keywords: 

Wed 01 Mar 2017 09:24:29 PM UTC, comment #5: 

Since there is no way this can be reproduced, it can't be fixed => Closing (which does not mean it's fixed).
Feel free to reopen if you can come up with new info that would enable someone to reproduce the issue.

Philippe Joyez <pjoyez>
Group Member
Wed 30 Nov 2016 08:15:52 PM UTC, comment #4: 

Thanks for the advice, I will have a look at the suggested material.

However, let me elaborate on usable and (semi-)automated bug reports: Correct me if I am wrong, but texmacs has:
- access to the last saved copy of a file I was working on prior to the crash
- history of whatever actions I took (otherwise undo could not have worked)

Thus, from my admittedly naive (non-programmer) perspective, it seems not understandable why texmacs itself could not provide the file that was worked on and the actions that lead to the crash (semi-)automatically  -- perhaps it could ask the user if he is OK with sending both to the developers to debug, or try to go through the actions step-by-step with the user to aid him at identifying the bug (e.g. for the sake of producing a useful bug report).

Often times a crash happens after a long use of texmacs... and I cannot reconstruct it simply because I cannot possibly remember all I have done.

Is the above a sci-fi? :-)

Peter Rapcan <peterrapcan>
Wed 30 Nov 2016 07:57:17 PM UTC, comment #3: 

Please lookup "how to write good bug reports"; you will find many useful advices. Among them, giving precise steps -and, if needed, sample files- so that someone can reproduce the problem is essential: If nobody can reproduce your problem there is no way it can be investigated, ever.

Now let me answer your questions:

-the backtraces you provide give a vague idea of where the program crashed, but no hint whatsoever of WHY it crashed, which is what we need if we want to fix it.

-Could a program collect all the relevant data for debugging a crash? No. On their own, programs simply cannot collect all the information that is being processed and which leads to the crash. For investigating such a crash one needs to use specialized tools such as a debugger.


Philippe Joyez <pjoyez>
Group Member
Wed 30 Nov 2016 04:52:34 PM UTC, comment #2: 

Shouldn't the default log (included) contain sufficient information? Can this be made a default functionality? I think that would help squash many bugs!

To your question, as far as I remember you wold need to launch a mathematica session on the specific document I was working on. I was hoping that the included error message provides sufficient information.

Peter Rapcan <peterrapcan>
Wed 30 Nov 2016 04:07:38 PM UTC, comment #1: 

steps to reproduce?

Philippe Joyez <pjoyez>
Group Member
Thu 07 Jul 2016 07:40:38 PM UTC, original submission:  

/Applications/TeXmacs.app/Contents/MacOS/TeXmacs
version1550
TeXmacs] With linked TrueType support
TeXmacs] debug-shell, Launching 'tm_mathematica'
TeXmacs] debug-shell, Launching 'tm_maxima 5.38.1 sbcl'
^[[ATeXmacs] debug-shell, Launching 'tm_mathematica'
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 2
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 12
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 2
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 12
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 2
TeXmacs] typeset-warning, Redefined eq:StatStateFormalSolution as 12
Throwing segmentation fault
-------------------------------------------------
Error message:
  segmentation fault

System information:
  TeXmacs version  : 1.99.4
  Built by         : Texmacs
  Building date    : Dec 17 2015
  Operating system : darwin10.3.1
  Vendor           : apple
  Processor        : i686
  Crash date       : Thu Jul  7 21:35:56 CEST 2016

Editor status:
  Root path          : [ 1 ]
  Current path       : [ 1, 112, 8, 4 ]
  Shifted path       : [ 1, 112, 8, 4 ]
  Physical selection : [ 1, 112, 8, 4 ] -- [ 1, 112, 8, 4 ]

Backtrace of C++ stack:
  1   TeXmacs                             0x00000001000633ae : get_crash_report(char const*) + 55
  2   TeXmacs                             0x0000000100007062 : tm_throw(char const*) + 64
  3   TeXmacs                             0x00000001008e400d : clean_exit_on_segfault(int) + 23
  4   libsystem_platform.dylib            0x00007fff90f8652a : _sigtramp() + 26
  5   ???                                 0x0000000000000000 : 0x0() + 0
  6   QtGui                               0x000000010158a601 : qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 257
  7   QtGui                               0x000000010158a6cb : qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 459
  8   QtGui                               0x000000010158a80b : qt_mac_set_modal_state(NSMenu*, bool) + 43
  9   QtGui                               0x000000010158e69d : QMenuBarPrivate::macUpdateMenuBarImmediatly() + 1053
  10  QtGui                               0x00000001015582d5 -[NSApplication(QApplicationIntegration) : qt_sendPostedMessage:]() + 277
  11  QtGui                               0x0000000101558571 -[NSApplication(QApplicationIntegration) : qt_filterEvent:]() + 145
  12  QtGui                               0x000000010155814d -[QNSApplication : sendEvent:]() + 45
  13  AppKit                              0x00007fff86029df2 -[NSApplication : run]() + 796
  14  QtGui                               0x0000000101562ff0 : QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1824
  15  QtCore                              0x00000001022f6064 : QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 68
  16  QtCore                              0x00000001022f6414 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 324
  17  QtCore                              0x00000001022f884c : QCoreApplication::exec() + 188
  18  TeXmacs                             0x00000001008e2f55 : TeXmacs_main(int, char**) + 13893
  19  TeXmacs                             0x000000010095b123 : new_call_back(void*, int, char**) + 35
  20  libguile.17.dylib                   0x00000001013a6500 : invoke_main_func() + 77
  21  libguile.17.dylib                   0x00000001013690b9 : c_body() + 37
  22  libguile.17.dylib                   0x00000001013f0d02 : scm_c_catch() + 610
  23  libguile.17.dylib                   0x000000010136905d : scm_i_with_continuation_barrier() + 210
  24  libguile.17.dylib                   0x0000000101369141 : scm_c_with_continuation_barrier() + 75
  25  libguile.17.dylib                   0x00000001013eee75 : scm_i_with_guile_and_parent() + 49
  26  libguile.17.dylib                   0x00000001013eee42 : scm_with_guile() + 36
  27  libguile.17.dylib                   0x00000001013a6494 : scm_boot_guile() + 69
  28  TeXmacs                             0x000000010095c1c6 : start_scheme(int, char**, void ()(int, char*)) + 74
  29  TeXmacs                             0x00000001008e3fac : main() + 1499
  30  TeXmacs                             0x000000010006cb90 : start() + 52

-------------------------------------------------
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

libc++abi.dylib: terminating with uncaught exception of type string
Abort trap: 6

Peter Rapcan <peterrapcan>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pjoyez (Posted a comment)
  • -email is unavailable- added by peterrapcan (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-03-01 pjoyez Open/ClosedOpen Closed
    2016-11-30 pjoyez StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code