Re: dlsym can't use handle returned by dlopen?

Markus Hoenicka writes: Don't mean to nag, but is there any news on this? just for the record: turns out this was a bug that got fixed in 6.3. See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129031 regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace

Re: dlsym can't use handle returned by dlopen?

Don't mean to nag, but is there any news on this? regards, Markus Markus Hoenicka writes: Jeremy Chadwick writes: As promised: http://www.malkavian.com/~jdc/myprog.tar.gz This test program indeed works as expected. However, this doesn't quite reflect the situation in libdbi. I

Re: dlsym can't use handle returned by dlopen?

Jeremy Chadwick writes: As promised: http://www.malkavian.com/~jdc/myprog.tar.gz This test program indeed works as expected. However, this doesn't quite reflect the situation in libdbi. I took your files and modified them accordingly, see:

Re: dlsym can't use handle returned by dlopen?

On Thu, Nov 13, 2008 at 09:00:21AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: I know that the .so's you're loading with dlopen() need to be built a specific way/with certain arguments, otherwise they won't work (I believe what I saw was dlsym() returning NULL).

Re: dlsym can't use handle returned by dlopen?

Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made

Re: dlsym can't use handle returned by dlopen?

Quoting Jeremy Chadwick [EMAIL PROTECTED]: I know that the .so's you're loading with dlopen() need to be built a specific way/with certain arguments, otherwise they won't work (I believe what I saw was dlsym() returning NULL). My symbol names were getting stomped on, and there was a compiler

Re: dlsym can't use handle returned by dlopen?

On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig

Re: dlsym can't use handle returned by dlopen?

On Thu, Nov 13, 2008 at 12:24:02AM -0800, Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's

Re: dlsym can't use handle returned by dlopen?

Quoting Jeremy Chadwick [EMAIL PROTECTED]: As promised: http://www.malkavian.com/~jdc/myprog.tar.gz I couldn't figure out what the gcc flag was that I needed to keep certain characters from getting prepended to the symbol names. I believe the char added was an underscore, but I could be

dlsym can't use handle returned by dlopen?

Hi, FreeBSD yeti.mininet 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Mon Aug 28 22:24:48 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/YETI i386 I'm trying to do the following: libdbi (http://libdbi.sourceforge.net) is a database abstraction layer which is linked as a shared object into

Re: dlsym can't use handle returned by dlopen?

On Thu, Nov 13, 2008 at 12:59:27AM +0100, Markus Hoenicka wrote: FreeBSD yeti.mininet 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Mon Aug 28 22:24:48 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/YETI i386 I'm trying to do the following: libdbi (http://libdbi.sourceforge.net) is a