public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anpaza at mail dot ru" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/6982] New: atexit() hooks are not called on exec() Date: Fri, 24 Oct 2008 18:47:00 -0000 [thread overview] Message-ID: <20081024184615.6982.anpaza@mail.ru> (raw) "man 3 exit" says, amongst other: ... The exit() function causes normal process termination and the value of status & 0377 is returned to the parent (see wait(2)). All functions registered with atexit(3) and on_exit(3) are called, in the reverse order of their registration. ... However, the atexit() hooks are never called if you invoke any of the exec*() functions. Steps to Reproduce: 1. Copy the example from 'man 3 atexit' to test.c 2. Modify it so that instead of "exit(EXIT_SUCCESS)" at the end we have, for example: execl ("/bin/ls", "ls"); 3. Compile and run the example Actual results: $ ./a.out ATEXIT_MAX = 2147483647 a.out test.c Expected results: $ ./a.out ATEXIT_MAX = 2147483647 That was all, folks a.out test.c I think it is a serious bug as it does not allow applications that rely on it to cleanup things that won't automatically cleanup during a normal process destruction. -- Summary: atexit() hooks are not called on exec() Product: glibc Version: 2.8 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: anpaza at mail dot ru CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=6982 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2008-10-24 18:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-24 18:47 anpaza at mail dot ru [this message] 2008-10-24 18:52 ` [Bug libc/6982] " drepper at redhat dot com 2008-10-24 18:54 ` anpaza at mail dot ru
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=20081024184615.6982.anpaza@mail.ru \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).