> >> 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. Many thanks - this is probably what I'm really looking for. Again sorry for footer (still working on it) Dave W.
This electronic transmission is strictly confidential and intended solely for the addressee(s). If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this email. If you have received this email in error please notify the sender as soon as possible. Any views expressed within this email may not necessarily be the views held by Calrec Audio Ltd. Calrec Audio Ltd have taken measures to ensure this email is free from computer viruses, however it is recommended that you also employ anti-virus measures on your computer systems. Calrec Audio Ltd. Registered in England. Registration number: 02392336. WEEE registration number: WEE/JE0051TQ/PRO. Registered address: Nutclough Mill, Hebden Bridge, West Yorks, HX7 8EZ. _______________________________________________ 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
