oh Deva thanks but my original question is how does it designed to work in the first place? without hard coding
thanks On Jan 3, 8:23 pm, Deva R <[email protected]> wrote: > it is set from "DEBUG=<n>" of elfdata ('m not sure now that how its passed > from build/source) > > for quick debugging, you can hardcore debug_verbosity in below piece of code > > bionic/linker/linker.c => __linker_init() > > while(vecs[0] != 0) { > if(!strncmp((char*) vecs[0], "DEBUG=", 6)) { > debug_verbosity = atoi(((char*) vecs[0]) + 6); > } else if(!strncmp((char*) vecs[0], "LD_LIBRARY_PATH=", 16)) { > ldpath_env = (char*) vecs[0] + 16; > } > vecs++; > > > > > > > > > > On Mon, Jan 3, 2011 at 3:35 PM, allstars <[email protected]> wrote: > > hi > > I try to see more logs from dynamic linker /system/bin/linker > > > and I do as the README.txt says to use -DLINKER_DEBUG=1 in Android.mk > > > but I want to see more message from PRINT INFO TRACE macro > > > README.txt says > > > "You can increase the verbosity of debug traces by defining the DEBUG > > environment variable to a numeric value from 0 to 2. This will only > > affect new processes being launched." > > > how do I do this?? > > > I found that 'adb shell export DEBUG=2" cannot work > > because the __linker_init function won't be called again for later > > forked processes > > so the debug_verbosity cannot be set > > > and why /system/bin/linker won't be invoked by forked processes(i.e. > > my app)? > > even I have tried to load my custom jni lib > > > thanks > > > -- > > unsubscribe: > > [email protected]<android-porting%2Bunsubscribe@ > > googlegroups.com> > > website:http://groups.google.com/group/android-porting > > -- > Regards, > Devawww.bittoggler.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
