From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `su` segfaults
Date: Fri, 16 Feb 2024 19:47:00 +0100 [thread overview]
Message-ID: <20240216184700.796C524A98@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
New comment by balejk on void-packages repository
https://github.com/void-linux/void-packages/issues/48758#issuecomment-1949104026
Comment:
`# gdb --args su - user` does segfault but `bt` says "No stack". `gdb`
also prints "Detaching after fork from child process <PID>" -- could
that be the reason for the missing backtrace?
Unless I'm doing something wrong (`# ulimit -c unlimited; su - user`,
works for other binaries), there seems to be no core dumped either.
next prev parent reply other threads:[~2024-02-16 18:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 10:53 [ISSUE] " balejk
2024-02-16 11:06 ` classabbyamp
2024-02-16 15:24 ` sgn
2024-02-16 18:47 ` balejk [this message]
2024-02-18 6:42 ` sgn
2024-02-18 9:03 ` catinello
2024-02-18 9:05 ` catinello
2024-02-18 14:02 ` sgn
2024-02-18 14:22 ` sgn
2024-02-18 14:32 ` [ISSUE] [CLOSED] " sgn
2024-02-18 14:33 ` balejk
2024-02-18 14:34 ` sgn
2024-02-18 14:35 ` sgn
2024-02-18 14:36 ` sgn
2024-02-18 14:37 ` sgn
2024-02-18 14:41 ` balejk
2024-02-18 22:04 ` oreo639
2024-02-18 22:06 ` oreo639
2024-02-18 22:07 ` oreo639
2024-02-18 22:07 ` oreo639
2024-02-18 22:09 ` oreo639
2024-02-18 22:09 ` oreo639
2024-02-19 5:38 ` sgn
2024-02-19 5:42 ` sgn
2024-02-19 5:43 ` sgn
2024-02-19 5:56 ` oreo639
2024-02-19 5:58 ` oreo639
2024-02-19 6:01 ` oreo639
2024-02-19 6:02 ` oreo639
2024-02-19 6:02 ` oreo639
2024-02-19 6:04 ` oreo639
2024-02-19 6:04 ` oreo639
2024-02-19 6:06 ` oreo639
2024-02-19 6:07 ` oreo639
2024-02-19 11:37 ` oreo639
2024-02-19 11:57 ` oreo639
2024-02-20 2:56 ` oreo639
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=20240216184700.796C524A98@inbox.vuxu.org \
--to=balejk@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).