public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schaudhu at blackrock dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3457] New: popen fails in sighandler after double free or corruption Date: Fri, 03 Nov 2006 23:56:00 -0000 [thread overview] Message-ID: <20061103235615.3457.schaudhu@blackrock.com> (raw) Please examine the following atomic example: #include <iostream> #include <signal.h> #include <sys/signal.h> using std::cout; using std::endl; void handler( int sig, siginfo_t *info, void *ctx ) { cout << "Got " << sig << " signal." << endl; popen( "/bin/ps", "r" ); cout << "Finished." << endl; } int main() { struct sigaction action; action.sa_sigaction = &handler; sigfillset( &action.sa_mask ); action.sa_flags = SA_RESETHAND | SA_SIGINFO | SA_ONSTACK; sigaction( SIGABRT, &action, NULL ); sigaction( SIGQUIT, &action, NULL ); sigaction( SIGILL, &action, NULL ); sigaction( SIGTRAP, &action, NULL ); sigaction( SIGABRT, &action, NULL ); sigaction( SIGFPE, &action, NULL ); sigaction( SIGBUS, &action, NULL ); sigaction( SIGSEGV, &action, NULL ); sigaction( SIGSYS, &action, NULL ); sigaction( SIGXCPU, &action, NULL ); sigaction( SIGXFSZ, &action, NULL ); void *p = ::malloc( 1 ); ::free( p ); ::free( p ); return 0; } With older versions of glibc, this produces: Got 11 signal. Finished. Segmentation fault (core dumped) With newer versions of glibc, this HANGS after producing: *** glibc detected *** double free or corruption (fasttop): 0x0804a008 *** Got 6 signal. The only way to terminate it is to forcibly kill the process. Using system() instead of popen() works okay. Can someone please investigate? Thanks! -- Summary: popen fails in sighandler after double free or corruption Product: glibc Version: 2.4 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: schaudhu at blackrock dot com CC: glibc-bugs at sources dot redhat dot com,schaudhu at blackrock dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3457 ------- 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:[~2006-11-03 23:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-03 23:56 schaudhu at blackrock dot com [this message] 2006-11-03 23:57 ` [Bug libc/3457] " schaudhu at blackrock dot com 2006-11-04 0:03 ` drepper at redhat dot com
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=20061103235615.3457.schaudhu@blackrock.com \ --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).