mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: Cody Wetzel <codyawetzel@gmail.com>
Cc: Natanael Copa <ncopa@alpinelinux.org>,
	musl@lists.openwall.com, Markus Wichmann <nullplan@gmx.net>
Subject: Re: [musl] Segmentation fault musl 1.2.4
Date: Thu, 4 Jan 2024 15:48:11 +0100	[thread overview]
Message-ID: <20240104144811.GO1427497@port70.net> (raw)
In-Reply-To: <CAFj3ykcn8F0w-Wkki4eZQ6-vDiz4oo9ZjhMiM41KJa=PR11eZA@mail.gmail.com>

* Cody Wetzel <codyawetzel@gmail.com> [2024-01-03 11:20:29 -0600]:
> Hello musl team,
> 
> I tried getting a core dump but I'm not sure if I'm doing something wrong...
> 
> / # cat /proc/sys/kernel/core_pattern/tmp/core-%e-%s-%u-%g-%p-%t/ #
> apk upgrade busybox
> --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
> --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/communityfetch
> https://dl-cdn.alpinelinux.org/alpine/v3.18/community/armv7/APKINDEX.tar.gzfetch
> https://dl-cdn.alpinelinux.org/alpine/v3.18/main/armv7/APKINDEX.tar.gzfetch
> https://dl-cdn.alpinelinux.org/alpine/v3.17/main/armv7/APKINDEX.tar.gzfetch
> https://dl-cdn.alpinelinux.org/alpine/v3.17/community/armv7/APKINDEX.tar.gz(1/3)
> Upgrading busybox (1.35.0-r29 -> 1.36.1-r5)Executing
> busybox-1.36.1-r5.post-upgrade(2/3) Upgrading busybox-binsh
> (1.35.0-r29 -> 1.36.1-r5)(3/3) Upgrading ssl_client (1.35.0-r29 ->
> 1.36.1-r5)Executing busybox-1.36.1-r5.triggerOK: 5 MiB in 15 packages/
> # apk upgrade musl
> --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
> --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/community(1/1)
> Upgrading musl (1.2.3-r5 -> 1.2.4-r2)OK: 5 MiB in 15 packages/ # apk
> upgrade rust --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
> --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/communitySegmentation
> fault/ # apk -hSegmentation fault/ # ls /tmp/core*Segmentation fault/
> # cd /tmp/tmp # lsSegmentation fault

i'd

# cp /lib/ld-musl-armhf.so.1 /tmp
# apk add gdb musl-dbg apk-tools-static

then upgrade musl using apk.static, then debug via

# /tmp/ld-musl-armhf.so.1 /usr/bin/gdb --args ls -l /tmp

or analyze a core dump, you can always install more debug tools
via apk.static and run commands using the old ld-musl-armhf.so.1

in gdb, you want to do

bt
disas $pc-40,+80
info reg
info proc map

as a starting point and post the results.

strace output can be useful too as well as readelf -aW of ld.so
depending on what is going on.

  parent reply	other threads:[~2024-01-04 14:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 21:53 Cody Wetzel
2023-12-21  3:38 ` Rich Felker
2023-12-21  4:15   ` Rich Felker
2023-12-21  7:57 ` Markus Wichmann
2023-12-21 18:39   ` Cody Wetzel
2023-12-21 21:25     ` Natanael Copa
2023-12-21 21:57       ` Cody Wetzel
2024-01-03 17:20         ` Cody Wetzel
2024-01-03 17:26           ` Leah Neukirchen
2024-01-03 18:00             ` Cody Wetzel
2024-01-04 14:48           ` Szabolcs Nagy [this message]
2024-01-10 15:59             ` Cody Wetzel
2024-01-11 17:03               ` Szabolcs Nagy
2024-01-11 18:19                 ` Cody Wetzel
2024-01-12 18:57                   ` Szabolcs Nagy
2024-01-12 23:10                     ` Cody Wetzel
2024-01-15 22:30                       ` Szabolcs Nagy
2024-01-16 15:21                         ` Cody Wetzel
2024-01-16 18:29                           ` Szabolcs Nagy
2024-01-16 18:53                             ` Cody Wetzel
2024-01-16 20:45                             ` Rich Felker
2024-01-30 10:43                               ` Szabolcs Nagy
2024-01-30 15:37                                 ` Rich Felker
2024-01-30 20:17                                   ` [musl] Fixing ELF loader for systems with oversized pages [was: Re: [musl] Segmentation fault musl 1.2.4] Rich Felker
2023-12-22  2:20 ` [musl] Segmentation fault musl 1.2.4 Jeffrey Walton
2023-12-22  2:22   ` Jeffrey Walton

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=20240104144811.GO1427497@port70.net \
    --to=nsz@port70.net \
    --cc=codyawetzel@gmail.com \
    --cc=musl@lists.openwall.com \
    --cc=ncopa@alpinelinux.org \
    --cc=nullplan@gmx.net \
    /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).