From: haary <haary@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lagrange: Segmentation fault
Date: Mon, 20 Sep 2021 13:30:48 +0200 [thread overview]
Message-ID: <20210920113048.tkSrCtZZa2IqU4YzPuaRd1Wd_F3P4syv1dF2-awfBxA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33032@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
New comment by haary on void-packages repository
https://github.com/void-linux/void-packages/issues/33032#issuecomment-922845431
Comment:
```
Thread 1 "lagrange" received signal SIGSEGV, Segmentation fault.
decodeBytes_MultibyteChar (bytes=0x498000003aa <error: Cannot access memory at address 0x498000003aa>, end=0x0,
ch_out=ch_out@entry=0x7fffffffdc8c) at ../lib/the_Foundation/src/string.c:927
927 ../lib/the_Foundation/src/string.c: Datei oder Verzeichnis nicht gefunden.
(gdb) backtrace
#0 decodeBytes_MultibyteChar (bytes=0x498000003aa <error: Cannot access memory at address 0x498000003aa>, end=0x0,
ch_out=ch_out@entry=0x7fffffffdc8c) at ../lib/the_Foundation/src/string.c:927
#1 0x0000555555577460 in findLoc_GmRun (d=0x5555590381d0, pos=...) at ../src/gmdocument.c:2063
#2 0x00005555555774d4 in findLoc_GmDocument (d=<optimized out>, pos=...) at ../src/gmdocument.c:1910
#3 0x00005555555947b9 in sourceLoc_DocumentWidget_ (d=d@entry=0x5555556becc0, pos=...) at ../src/ui/documentwidget.c:2006
#4 0x0000555555594e1e in beginMarkingSelection_DocumentWidget_ (d=d@entry=0x5555556becc0, pos=...) at ../src/ui/documentwidget.c:3355
#5 0x000055555559df15 in processEvent_DocumentWidget_ (d=0x5555556becc0, ev=<optimized out>) at ../src/ui/documentwidget.c:3751
#6 0x00005555555f074b in dispatchEvent_Widget (d=d@entry=0x5555556becc0, ev=ev@entry=0x7fffffffe080) at ../src/ui/widget.c:1002
#7 0x00005555555ed4a0 in processEvent_Window (d=0x5555556ea3f0, ev=0x7fffffffe080, ev@entry=0x7fffffffe170) at ../src/ui/window.c:885
#8 0x0000555555567c05 in processEvents_App (eventMode=eventMode@entry=waitForNewEvents_AppEventMode) at ../src/app.c:1261
#9 0x0000555555568c57 in run_App_ (d=<optimized out>) at ../src/app.c:1367
#10 run_App (argc=argc@entry=1, argv=argv@entry=0x7fffffffe3d8) at ../src/app.c:1456
#11 0x0000555555561a30 in main (argc=1, argv=0x7fffffffe3d8) at ../src/main.c:78
```
next prev parent reply other threads:[~2021-09-20 11:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 7:05 [ISSUE] " haary
2021-09-20 9:59 ` paper42
2021-09-20 10:44 ` haary
2021-09-20 10:49 ` paper42
2021-09-20 11:30 ` haary [this message]
2021-09-25 18:14 ` paper42
2021-09-25 20:48 ` ericonr
2021-10-02 1:17 ` sgn
2021-10-02 1:45 ` sgn
2021-10-02 23:20 ` paper42
2021-10-03 4:58 ` skyjake
2021-10-03 5:07 ` skyjake
2021-10-03 16:36 ` [ISSUE] [CLOSED] " sgn
2021-10-03 16:37 ` sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210920113048.tkSrCtZZa2IqU4YzPuaRd1Wd_F3P4syv1dF2-awfBxA@z \
--to=haary@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).