On Tuesday 16 Mar 2004 1:22 am, George Anzinger wrote:Pardon my question. I've lost track of the thread and the available context
Amit S. Kale wrote:
On Friday 12 Mar 2004 1:33 pm, George Anzinger wrote:You have a better solution?
Amit S. Kale wrote:I have seen that. It's too messy!
On Friday 12 Mar 2004 2:58 am, George Anzinger wrote:Possibly I can help here. I did it for the mm version. It does require
Amit S. Kale wrote:No! It's not present in kgdb heavy also. All you can do is set $pc,
~
Is this capability in kgdb lite? It was one of the last things I addedcontext anyp fun() will push arguments on stack over the place where irq occured,
p fun()
which is exactly how it'll run.
to -mm version.
continue.
a couple of asm bits and it sort of messes up the set/fetch memory, but
it does do the job.
Nope.
I think this feature is very likely to be abused by programmers. They do deserve suffering if they choose to shoot at their own feet.
Kernel programmers have to be aware of implementation of this feature if they choose to call arbitrary functions. This includes knowing whether interrupts are disabled, handling of exceptions in gdb called functions, whether other processors run, that breakpoints are disabled. Given that kgdb is used for learning the kernel, such features are best kept aside.
-Amit