>> e.g. if I use grep to find occurrences of say "gpio_request", I get a
>> long list to search through, but I know many of the files are not even
>> compiled into my build. Is there an easy way to find the real place
>> where a function is coded for my particular build?
I use to look for it in the object files:
find . -name "*.o" -o -name "*.ko" \
| xargs nm -o 2> /dev/null | grep -w <function-or-variable>
Same for error messages: use "strings -f" on object files, instead of looking
in the sources.
/alessandro
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
