From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Exception handling and stack unwinds segfault on aarch64-musl
Date: Tue, 13 Oct 2020 01:44:43 +0200 [thread overview]
Message-ID: <20201012234443.UMjHIN5EY3P2H9uIQuqNAQ0RaEu5s6IU1WH316MDhXU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25535@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3442 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/25535#issuecomment-707399563
Comment:
```
==13821== Memcheck, a memory error detector
==13821== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==13821== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==13821== Command: ./a.out
==13821==
==13821== Invalid read of size 1
==13821== at 0x40607DC: strlen (strlen.c:16)
==13821== by 0x4F9271B: get_cie_encoding (unwind-dw2-fde.c:300)
==13821== by 0x4F92BAB: classify_object_over_fdes (unwind-dw2-fde.c:656)
==13821== by 0x4F9340B: init_object (unwind-dw2-fde.c:777)
==13821== by 0x4F9340B: search_object (unwind-dw2-fde.c:989)
==13821== by 0x4F93D63: _Unwind_Find_registered_FDE (unwind-dw2-fde.c:1066)
==13821== by 0x4F93D63: _Unwind_Find_FDE (unwind-dw2-fde-dip.c:458)
==13821== by 0x4F907A7: uw_frame_state_for (unwind-dw2.c:1257)
==13821== by 0x4F917CB: uw_init_context_1 (unwind-dw2.c:1586)
==13821== by 0x4F91DFF: _Unwind_RaiseException (unwind.inc:93)
==13821== by 0x4DD3B33: __cxa_throw (in /usr/lib/libstdc++.so.6.0.28)
==13821== by 0x108BC7: main (in /home/danh/a.out)
==13821== Address 0x2093162 is not stack'd, malloc'd or (recently) free'd
==13821==
==13821==
==13821== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==13821== Access not within mapped region at address 0x2093162
==13821== at 0x40607DC: strlen (strlen.c:16)
==13821== by 0x4F9271B: get_cie_encoding (unwind-dw2-fde.c:300)
==13821== by 0x4F92BAB: classify_object_over_fdes (unwind-dw2-fde.c:656)
==13821== by 0x4F9340B: init_object (unwind-dw2-fde.c:777)
==13821== by 0x4F9340B: search_object (unwind-dw2-fde.c:989)
==13821== by 0x4F93D63: _Unwind_Find_registered_FDE (unwind-dw2-fde.c:1066)
==13821== by 0x4F93D63: _Unwind_Find_FDE (unwind-dw2-fde-dip.c:458)
==13821== by 0x4F907A7: uw_frame_state_for (unwind-dw2.c:1257)
==13821== by 0x4F917CB: uw_init_context_1 (unwind-dw2.c:1586)
==13821== by 0x4F91DFF: _Unwind_RaiseException (unwind.inc:93)
==13821== by 0x4DD3B33: __cxa_throw (in /usr/lib/libstdc++.so.6.0.28)
==13821== by 0x108BC7: main (in /home/danh/a.out)
==13821== If you believe this happened as a result of a stack
==13821== overflow in your program's main thread (unlikely but
==13821== possible), you can try to increase the size of the
==13821== main thread stack using the --main-stacksize= flag.
==13821== The main thread stack size used in this run was 8388608.
==13821==
==13821== HEAP SUMMARY:
==13821== in use at exit: 74,233 bytes in 12 blocks
==13821== total heap usage: 14 allocs, 2 frees, 74,345 bytes allocated
==13821==
==13821== LEAK SUMMARY:
==13821== definitely lost: 0 bytes in 0 blocks
==13821== indirectly lost: 0 bytes in 0 blocks
==13821== possibly lost: 174 bytes in 2 blocks
==13821== still reachable: 74,059 bytes in 10 blocks
==13821== of which reachable via heuristic:
==13821== stdstring : 30 bytes in 1 blocks
==13821== suppressed: 0 bytes in 0 blocks
==13821== Rerun with --leak-check=full to see details of leaked memory
==13821==
==13821== For lists of detected and suppressed errors, rerun with: -s
==13821== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
```
next prev parent reply other threads:[~2020-10-12 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 1:02 [ISSUE] " duncancmt
2020-10-12 19:10 ` jnbr
2020-10-12 23:44 ` sgn [this message]
2020-10-12 23:45 ` sgn
2020-10-14 10:17 ` jnbr
2020-10-14 19:34 ` jnbr
2020-10-14 19:34 ` jnbr
2020-10-16 18:29 ` [ISSUE] [CLOSED] " jnbr
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=20201012234443.UMjHIN5EY3P2H9uIQuqNAQ0RaEu5s6IU1WH316MDhXU@z \
--to=sgn@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).