Info about which modules fires a hook is very handy, for example, if you working on improving performance - maybe there is a module which isn't necessary to be enable and you may disable it.
Edit: Thanks to @jaroslaw.kaminski for feedback :) I forgot " ' " at the end of line oO
Let's track hook_menu:
- drush eval 'print_r(module_implements("menu"));'
There is a better way to do this found by @Drupby:
- #Drush 5.9 has implemented two new commands:
- #List implementations of a given hook and explore source of specified one.
- drush fnh anyhook
- #Show the source of specified function or method.
- drush fnv