GNU TeXmacs - Bugs: bug #49652, 1.99.5 segfault due to a change in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #49652: 1.99.5 segfault due to a change in r 10067
Submitter: | Philippe Joyez <pjoyez> | ||
Submitted: | Sat 19 Nov 2016 02:25:29 PM UTC | ||
Category: | None | Priority: | 5 - Normal |
Item Group: | None | Status: | Confirmed |
Privacy: | Public | Assigned to: | None |
Originator Name: | Open/Closed: | Closed | |
Release: | None | Release: | |
Fixed Release: | None | Fixed Release: | |
Keywords: |
Wed 01 Mar 2017 09:17:58 PM UTC, comment #3: |
Philippe Joyez <pjoyez> |
Fri 02 Dec 2016 09:56:19 PM UTC, comment #2: Upon inspection of frame 0 it appears that the index i has run off. If I prevent this by applying the following patch
|
Philippe Joyez <pjoyez> |
Fri 02 Dec 2016 09:23:36 PM UTC, comment #1: Here is a bt after the crash: the stack seems corrupted (the bt is not always, but this one is frequent).
|
Philippe Joyez <pjoyez> |
Sat 19 Nov 2016 02:25:29 PM UTC, original submission:
I found by chance a reproducible way to have texmacs 1.99.5 segfaulting on linux and windows.
|
Philippe Joyez <pjoyez> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-03-01 | pjoyez | Open/Closed | Open | Closed |
Powered by Savane 3.13-02a9.
Corresponding source code
Actually, prior to rev 10067 that function was simply not called at all to display the help widget (and thus it had no reason to trigger the bug)...
Anyway the bug was prevented to occur by r10609-10611
but it does trigger some
TeXmacs] warning: invalid cursor position [ 1, 0, 0, 1, 1, 1, 0, 0, 95 ].
when the cursor is placed and moved around in the source code of the function that is displayed in the widget.
I'm closing nevertheless since the crash is gone.