public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jg at jguk dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26728] New: Change _dl_fatal_printf to dump core file
Date: Tue, 13 Oct 2020 10:09:12 +0000	[thread overview]
Message-ID: <bug-26728-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26728

            Bug ID: 26728
           Summary: Change _dl_fatal_printf to dump core file
           Product: glibc
           Version: 2.34
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: jg at jguk dot org
  Target Milestone: ---

Could _dl_fatal_printf be considered to change to call raise a signal that
dumps the core instead of _exit(127)?

As the code is an assert(), perhaps SIGTRAP or SIGABRT is best?

On my computer any C program compiled with assert(0) dumps a core file, but
this glibc issue assert does not dump a core file.

Inconsistency detected by ld.so: ../elf/dl-tls.c: 481: _dl_allocate_tls_init:
Assertion `listp->slotinfo[cnt].gen <= GL(dl_tls_generation)' failed!
Command exited with non-zero status 127

This came up while discussing this issue
https://sourceware.org/bugzilla/show_bug.cgi?id=19329


This is my test program

$ ./a
a: a.c:6: main: Assertion `0' failed.
Aborted (core dumped)


$ cat a.c
// gcc -Wall -o a a.c
#include <assert.h>

int main()
{
    assert(0);
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-10-13 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 10:09 jg at jguk dot org [this message]
2020-10-13 10:16 ` [Bug dynamic-link/26728] " schwab@linux-m68k.org
2020-10-13 10:17 ` fweimer at redhat dot com
2020-10-13 10:26 ` jg at jguk dot org

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=bug-26728-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).