From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zathura and synctex: segfault
Date: Thu, 01 Jul 2021 10:06:24 +0200 [thread overview]
Message-ID: <20210701080624.DzJYg-JqsGEhSsAgCqLM7JY6PbQ_J7O96mIsx---M68@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31722@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/31722#issuecomment-872022593
Comment:
I use the `vimtex` plugin, which generates the synctex file, see https://github.com/lervag/vimtex (you also need `xdotool`).
Am I doing this right? it is running for several minutes without any new output, just maxing out a core..
```
$ DEBUGINFOD_URLS="https://debuginfod.s.voidlinux.org" gdb --args zathura --synctex-forward 1:1:'test.tex' 'test.pdf'
GNU gdb (GDB) 10.2
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from zathura...
(No debugging symbols found in zathura)
(gdb) run
Starting program: /usr/bin/zathura --synctex-forward 1:1:test.tex test.pdf
[New LWP 19565]
[New LWP 19566]
[New LWP 19567]
[New LWP 19568]
[LWP 19568 exited]
[LWP 19567 exited]
[New LWP 19692]
[New LWP 19693]
[LWP 19693 exited]
[LWP 19692 exited]
```
next prev parent reply other threads:[~2021-07-01 8:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 10:00 [ISSUE] " dkwo
2021-06-30 14:25 ` ericonr
2021-06-30 14:37 ` ericonr
2021-06-30 14:58 ` dkwo
2021-06-30 14:59 ` dkwo
2021-06-30 19:25 ` ericonr
2021-07-01 8:06 ` dkwo [this message]
2021-07-01 13:13 ` dkwo
2021-07-07 16:20 ` dkwo
2021-07-15 16:29 ` dkwo
2021-07-15 17:22 ` ericonr
2021-07-15 17:52 ` ericonr
2021-07-15 18:01 ` dkwo
2021-07-15 18:01 ` dkwo
2021-07-15 18:02 ` dkwo
2021-07-15 18:10 ` zathura and synctex: segfault with musl 1.2 dkwo
2021-07-15 18:11 ` ericonr
2021-07-15 18:15 ` ericonr
2021-07-15 18:22 ` richfelker
2021-07-15 18:24 ` richfelker
2021-07-15 18:24 ` richfelker
2021-07-15 18:26 ` dkwo
2021-07-15 18:27 ` richfelker
2021-07-15 18:28 ` dkwo
2021-07-15 18:29 ` richfelker
2021-07-15 18:31 ` dkwo
2021-07-15 18:31 ` ericonr
2021-07-15 18:36 ` ericonr
2021-07-15 18:37 ` ericonr
2021-07-15 18:41 ` [ISSUE] [CLOSED] " ericonr
2021-07-15 19:04 ` ericonr
2021-07-15 19:12 ` ericonr
2021-07-15 20:06 ` dkwo
2021-07-15 20:34 ` ericonr
2021-07-15 20:38 ` dkwo
2021-07-15 20:49 ` richfelker
2021-07-15 20:58 ` dkwo
2021-07-15 21:10 ` richfelker
2021-07-17 10:28 ` dkwo
2021-07-17 19:53 ` ericonr
2021-07-17 20:07 ` ericonr
2021-07-18 10:24 ` dkwo
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=20210701080624.DzJYg-JqsGEhSsAgCqLM7JY6PbQ_J7O96mIsx---M68@z \
--to=dkwo@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).