unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 58923@debbugs.gnu.org
Subject: bug#58923: Malformed core dumps on Guix System
Date: Wed, 02 Nov 2022 11:31:26 +0100	[thread overview]
Message-ID: <87iljxwsu9.fsf@gnu.org> (raw)
In-Reply-To: <87fsf4gukr.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 31 Oct 2022 11:23:48 +0100")

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

> 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.

I never encountered that issue, although I’ve had to look a lot at core
dumps over time.  :-)

--8<---------------cut here---------------start------------->8---
$ gcc test.c
$ ulimit -c unlimited 
$ ./a.out
Segmentation fault (core dumped)
$ gdb a.out core
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from a.out...
(No debugging symbols found in a.out)
[New LWP 23407]
Core was generated by `./a.out'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000401106 in main ()
(gdb) bt
#0  0x0000000000401106 in main ()
(gdb) quit
--8<---------------cut here---------------end--------------->8---

Could it have to do with /proc/sys/kernel/core_pattern or with the fact
that your /tmp file system was full or something?  What if you try to
have the core dump on another file system?

Thanks,
Ludo’.




  reply	other threads:[~2022-11-02 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 10:23 bug#58923: Malformed core dumps on Guix System Mathieu Othacehe
2022-11-02 10:31 ` Ludovic Courtès [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iljxwsu9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=58923@debbugs.gnu.org \
    --cc=othacehe@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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).