public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gauryogesh.nsit at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15291] New: cannot enable executable stack as shared object requires Date: Thu, 21 Mar 2013 09:06:00 -0000 [thread overview] Message-ID: <bug-15291-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15291 Bug #: 15291 Summary: cannot enable executable stack as shared object requires Product: glibc Version: 2.14 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: gauryogesh.nsit@gmail.com CC: drepper.fsp@gmail.com Classification: Unclassified I have taken the patch provided for the issue "do_lookup_x may access dangling memory" fixed in bugzilla http://sourceware.org/bugzilla/show_bug.cgi?id=13579 With this patch crash issue of "do_lookup_x may access dangling memory" gets solved but I am getting one more new issue on my MIPS target. error : ./libjpeg.so: cannot enable executable stack as shared object requires: Invalid argument. -------------------------------------------------------------- cat test.c #include <stdio.h> #include <dlfcn.h> #include <pthread.h> void *handle; static void *thread_abc() { handle = dlopen ("./libjpeg.so", RTLD_LAZY | RTLD_GLOBAL); printf ("<thread_abc> Handle:%p\n", handle); dlclose (handle); return NULL; } static void *thread_xyz() { handle = dlopen ("./libjpeg.so", RTLD_LAZY | RTLD_GLOBAL); printf ("<thread_abc> Handle:%p\n", handle); dlclose (handle); return NULL; } int main() { int i=0; handle = dlopen ("./libjpeg.so", RTLD_LAZY | RTLD_GLOBAL); printf ("<thread_abc> Handle:%p\n", handle); if((error=dlerror()) != NULL) printf("error : %s\n", error); if(handle==NULL) return 0; printf ("<thread_abc> Handle:%p\n", handle); dlclose (handle); printf ("Returning from main\n"); return 0; } ------------------------------------------------- When I check my libjpeg.so with readelf it didn't have any STACK frame $ mipsel-34kv3r1-linux-gnu-readelf -l libjpeg.so | grep "STACK" $ Furthermore, I checked that if I removed the patch for BUG 13579, then this issue is not occurring. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-03-21 9:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-21 9:06 gauryogesh.nsit at gmail dot com [this message] 2013-03-22 3:27 ` [Bug libc/15291] " gauryogesh.nsit at gmail dot com 2014-06-13 18:41 ` fweimer 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=bug-15291-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: 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).