From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: Crash using python in alpine with musl and confluent-kafka python library
Date: Thu, 24 Oct 2019 19:57:40 -0500 [thread overview]
Message-ID: <4242496b-9ade-6140-9321-d8ccc2a24a59@adelielinux.org> (raw)
In-Reply-To: <20191025003453.GS16318@brightrain.aerifal.cx>
[-- Attachment #1.1: Type: text/plain, Size: 2364 bytes --]
On 24/10/2019 19:34, Rich Felker wrote:
> On Fri, Oct 25, 2019 at 12:14:29AM +0000, Richard Lee wrote:
>> Thread 3 "rdk:main" received signal SIGSEGV, Segmentation fault.
>> [Switching to LWP 220]
>> __bin_chunk (self=0x559c68375130) at src/malloc/malloc.c:456
>> 456 src/malloc/malloc.c: No such file or directory.
>> (gdb) bt
>> #0 __bin_chunk (self=0x559c68375130) at src/malloc/malloc.c:456
>> #1 0x00007fe8f0b04d92 in trim (self=self@entry=0x559c683750d0, n=<optimized out>) at src/malloc/malloc.c:281
>> #2 0x00007fe8f0b05120 in malloc (n=<optimized out>) at src/malloc/malloc.c:328
>> #3 0x00007fe8f0b05238 in realloc (p=<optimized out>, n=<optimized out>) at src/malloc/malloc.c:375
>> #4 0x00007fe8ef963181 in ?? () from /usr/lib/librdkafka.so.1
>> #5 0x00007fe8ef9631cc in ?? () from /usr/lib/librdkafka.so.1
>> #6 0x00007fe8ef978770 in rd_kafka_ConfigResource_new () from /usr/lib/librdkafka.so.1
>> #7 0x00007fe8ef97a514 in ?? () from /usr/lib/librdkafka.so.1
>> #8 0x00007fe8ef977db5 in ?? () from /usr/lib/librdkafka.so.1
>> #9 0x00007fe8ef977665 in ?? () from /usr/lib/librdkafka.so.1
>> #10 0x00007fe8ef94513f in ?? () from /usr/lib/librdkafka.so.1
>> #11 0x00007fe8ef9479e9 in ?? () from /usr/lib/librdkafka.so.1
>> #12 0x00007fe8ef947a3c in ?? () from /usr/lib/librdkafka.so.1
>> #13 0x00007fe8ef946356 in ?? () from /usr/lib/librdkafka.so.1
>> #14 0x00007fe8ef9263f8 in ?? () from /usr/lib/librdkafka.so.1
>> #15 0x00007fe8f0b32f94 in start_c11 (p=<optimized out>) at src/thread/pthread_create.c:203
>> #16 0x00007fe8f0b3504d in __clone () at src/thread/x86_64/clone.s:22
>> Backtrace stopped: frame did not save the PC
>
> Can you supplement this report with a disassembly of the crash point
> showing the faulting instruction? Based on the above, my first guess
> would be a stack overflow, and if not that, heap corruption from out
> of bound writes somewhere else.
>
> Having debug symbols for librdkafka.so.1 might also be useful; it
> could at least give an idea what's going on when it crashes.
>
> Rich
Tiny note that we have librdkafka 1.2.0 in Adélie built with debug
symbols, if you wanted a simple way to get a chroot with them without
the hassle of rebuilding yourself.
Best,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-25 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 0:14 Richard Lee
2019-10-25 0:34 ` Rich Felker
2019-10-25 0:57 ` A. Wilcox [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=4242496b-9ade-6140-9321-d8ccc2a24a59@adelielinux.org \
--to=awilfox@adelielinux.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).