X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SARE_SUB_ENC_UTF8 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Fri, 15 Jan 2010 16:17:09 +0100 From: "Vincent R." To: Subject: Re: [cfe-dev] cygwin updates (was: dladdr and =?UTF-8?Q?Dl=5Finfo=29?= In-Reply-To: <20100115141828.GC4977@calimero.vinschen.de> References: <3ab31ceedb33b3519257e07931dbdaf5@mail.smartmobili.com> <4B4F7C90.4030509@x-ray.at> <4B4F82B1.3080605@users.sourceforge.net> <4B4F908D.2060709@x-ray.at> <20100115101927.GG22230@calimero.vinschen.de> <686aa375429ae2e4ea39acf503a6a617@mail.smartmobili.com> <20100115141828.GC4977@calimero.vinschen.de> Message-ID: X-Sender: forumer@smartmobili.com User-Agent: RoundCube Webmail/0.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, 15 Jan 2010 15:18:28 +0100, Corinna Vinschen > On Jan 15 11:40, Vincent R. wrote: >> It's not too difficult to add Dl_info definition (We will support only >> retrieving path name): >> >> typedef struct >> { >> const char *dli_fname[PATH_MAX]; /* Filename of defining object */ >> void *dli_fbase; /* NA */ >> const char *dli_sname; /* NA */ >> void *dli_saddr; /* NA */ >> } Dl_info; >> >> >> int dladdr(void *addr, Dl_info *info) >> { >> // see >> http://trac.enlightenment.org/e/browser/trunk/PROTO/evil/src/lib/dlfcn/dlfcn.c >> // for an implementation >> } > > The implementation won't work on Cygwin for functions exported by the > Cygwin DLL itself. At least not as you expect it to work. Every such > symbol will return the application's pathname in dli_fname. The reason > is the way the functions are exported from libcygwin.a. You always get > the address of the function stub linked statically to the executable. > I fear this needs more work for Cygwin. > I understand but I suppose it would work for other dlls and it's not important if it doesn't work for cygwin dll itself because until now you didn't need it. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple