From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zpaq segment faults
Date: Sat, 21 May 2022 20:27:50 +0200 [thread overview]
Message-ID: <20220521182750.A8s047xQ7h3Gee5ceNU6QQ4MevsvYaa_D9MZUWQXRZU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31080@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/31080#issuecomment-1133748070
Comment:
I can reproduce this:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 memcpy () at src/string/x86_64/memcpy.s:18
18 src/string/x86_64/memcpy.s: No such file or directory.
[Current thread is 1 (LWP 8176)]
#0 memcpy () at src/string/x86_64/memcpy.s:18
#1 0x00005619b0412cd5 in libzpaq::StringBuffer::read (this=0x7fb3de968d30, buf=<optimized out>, n=16384) at libzpaq.h:1472
#2 0x00005619b04335a5 in libzpaq::Compressor::compress (this=this@entry=0x7fb3de5f5790, n=n@entry=-1) at libzpaq.cpp:2930
#3 0x00005619b043bfa6 in libzpaq::compressBlock (in=in@entry=0x7fb3de968d30, out=out@entry=0x7fb3de968d78, method_=<optimized out>, filename=0x7fb3de9686a0 "jDC20220521182512d0000000001", comment=0x7fb3de968de0 "jDC\001", dosha1=dosha1@entry=true) at libzpaq.cpp:7718
#4 0x00005619b0400c96 in compressThread (arg=0x7ffcb714f490) at /usr/include/c++/8.2/bits/basic_string.h:2281
#5 0x00007fb3de9208ce in start (p=0x7fb3de610ac0) at src/thread/pthread_create.c:195
#6 0x00007fb3de92d9fb in __clone () at src/thread/x86_64/clone.s:22
Backtrace stopped: frame did not save the PC
```
prev parent reply other threads:[~2022-05-21 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 19:37 [ISSUE] " Mek101
2021-05-23 23:12 ` ericonr
2021-05-24 10:30 ` Mek101
2022-05-20 2:12 ` github-actions
2022-05-21 18:27 ` paper42 [this message]
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=20220521182750.A8s047xQ7h3Gee5ceNU6QQ4MevsvYaa_D9MZUWQXRZU@z \
--to=paper42@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).