From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4FE863857C5E; Sat, 27 Nov 2021 12:01:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4FE863857C5E From: "stsp at users dot sourceforge.net" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/11767] RFE: dlopen of in-memory ET_DYN or ET_EXEC object Date: Sat, 27 Nov 2021 12:01:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: stsp at users dot sourceforge.net X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ppluzhnikov at google dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2021 12:01:50 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11767 Stas Sergeev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stsp at users dot sourcefo= rge.net --- Comment #25 from Stas Sergeev --- (In reply to Gregory P. Smith from comment #21) > Created attachment 7266 [details] > attachment-3251-0.html This attachment seems broken. It has some html file instead of a patch, or is it just me? > There is no writable storage or the ability to mount any in the situation > Paul and I are looking to support. dlopen_with_offset seems to be a quite limited solution, as even fd is not always available. What do people think about dlopen_fstream(FILE *f, int flags); that can work with file streams? One can use fopencookie() to create any weird file stream, or one can use fmemopen() to read from memory. --=20 You are receiving this mail because: You are on the CC list for the bug.=