Hi,
I used uclibc-0.9.29,
/*dltest.c*/
#include stdio.h
#include dlfcn.h
#define MYLIB /flash/lib/libdev.so
int main (void){
void *handle;
while (1){
handle = dlopen (MYLIB, RTLD_LAZY);
if (!handle){
fputs (dlerror(), stderr);
exit (1);
Hi,
I used uclibc-0.9.29,
/*dltest.c*/
#include stdio.h
#include dlfcn.h
#define MYLIB /flash/lib/libdev.so
int main (void){
void *handle;
while (1){
handle = dlopen (MYLIB, RTLD_LAZY);
if (!handle){
fputs (dlerror(), stderr);
exit
Do you mean the change of dl_cleanup as below:
http://sources.busybox.net/index.py/trunk/uClibc/ldso/libdl/libdl.c?r1=23552r2=23853diff_format=h
Thanks,
To: xjt...@hotmail.com
CC: uclibc@uclibc.org
Subject: Re: dlopen/dlclose caused memory leak?
From: joakim.tjernl...@transmode.se
No, I think it was this one:
http://sources.busybox.net/index.py/trunk/uClibc/ldso/ldso/dl-elf.c?r1=14417r2=14840
czy xjt...@hotmail.com wrote on 11/03/2009 13:37:56:
Do you mean the change of dl_cleanup as below:
Thanks for your quick reply,
This one has been applied to version 0.9.29
To: xjt...@hotmail.com
CC: uclibc@uclibc.org
Subject: RE: dlopen/dlclose caused memory leak?
From: joakim.tjernl...@transmode.se
Date: Wed, 11 Mar 2009 13:47:50 +0100
No, I think it was this one:
Hi,
I wonder if anyone using uclibc succesfully linked an application using
TCC. My binaries end up as:
ldd ./tcc
checking sub-depends for '/lib/libm.so.0'
libc.so.0 = /lib/libc.so.0 (0xb7f92000)
ld-uClibc.so.0 = /lib/ld-uClibc.so.0 (0xb7fe3000)
checking sub-depends for