Mulyadi and Sri Ram, Thanks for the inputs. I didn't know about the in_atomic() functions. But I am taking care not to cause bad things by checking if current is not null. > > The other way is to do code tracing by yourself. This method itself > can be done by the help of gdb or other debugger (break at the target > code and do backtracing) OR by doing manual code tracing. > Most of the times, I just end up tracing the code path manually from the source code. I have another question, though: Is it possible in gdb to break on all function calls? Would be useful. :) Thanks, -- Vimal -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
