all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: 58923@debbugs.gnu.org
Subject: bug#58923: Malformed core dumps on Guix System
Date: Mon, 31 Oct 2022 11:23:48 +0100	[thread overview]
Message-ID: <87fsf4gukr.fsf@gnu.org> (raw)


Hello,

Working on https://issues.guix.gnu.org/58733, I noticed that there is
something wrong with the core dumps we are generating on Guix System.

--8<---------------cut here---------------start------------->8---
mathieu@meije ~/tmp [env]$ cat test.c 
#include <stdio.h>
int main() {
	int *t = NULL;
	return *t;
}

mathieu@meije ~/tmp [env]$ gcc test.c 
mathieu@meije ~/tmp [env]$ ulimit -c unlimited
mathieu@meije ~/tmp [env]$ ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) unlimited

mathieu@meije ~/tmp [env]$ echo "/tmp/my-core-%p" | sudo tee /proc/sys/kernel/core_pattern
/tmp/my-core-%p

mathieu@meije ~/tmp [env]$ ./a.out 
Segmentation fault (core dumped)

mathieu@meije ~/tmp [env]$ gdb ./a.out /tmp/my-core-5622
...
BFD: warning: /tmp/my-core-5622 has a segment extending past end of file
...
Failed to read a valid object file image from memory.
Core was generated by `./a.out'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000401102 in main ()
(gdb) bt
#0  0x0000000000401102 in main ()
Backtrace stopped: Cannot access memory at address 0x7fff14e14168
--8<---------------cut here---------------end--------------->8---

The "has a segment extending past end of file" warning appears to be
problematic and the "bt" command does not work which makes core dump
generation a bit useless.

Thanks,

Mathieu




             reply	other threads:[~2022-10-31 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 10:23 Mathieu Othacehe [this message]
2022-11-02 10:31 ` bug#58923: Malformed core dumps on Guix System Ludovic Courtès
2022-11-02 11:25   ` Mathieu Othacehe
2022-11-02 14:18     ` zimoun
2022-11-03 11:21       ` Mathieu Othacehe
2022-11-10 10:14     ` Ludovic Courtès
2022-11-10 17:14       ` Mathieu Othacehe
2022-11-10 18:09         ` Maxim Cournoyer

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=87fsf4gukr.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=58923@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.