On 12-Dec-2002 Matthew Dillon wrote:
>:> function A calls function B which uses ecx as a loop index. The bad part is
>function B never
>:> saves/restores the value of ecx and function A starts dereferencing garbage.
>:>
>:> An informal sampling of my driver seems to indicate that ebx gets
>:> pu
:> function A calls function B which uses ecx as a loop index. The bad part is
:function B never
:> saves/restores the value of ecx and function A starts dereferencing garbage.
:>
:> An informal sampling of my driver seems to indicate that ebx gets
:> pushed/poped at entry/exit but ecx and edx do
On 10-Dec-2002 Chuck Tuffli wrote:
> I've been chasing down some weird panics in my CAM driver and have
> noticed that functions don't seem to save all register values before
> they modify them.
>
> For example, function A uses register ecx to hold the value of a pointer. Part way
>through,
> fu
In C for the IA32, EAX, ECX, and EDX are scratch registers. All other
registers must be saved and restored by the procedure.
Also keep in mind that the return value of a procedure is placed in
eax. If the return value is a 64 bit value, it is placed in eax and
edx.
On Tue, Dec 10, 2002 at 04:58:34PM +0100, [EMAIL PROTECTED] wrote:
> In message <[EMAIL PROTECTED]>, Chuck Tuffli write
> s:
> >I've been chasing down some weird panics in my CAM driver and have
> >noticed that functions don't seem to save all register values before
> >they modify them.
> >
> >For
In message <[EMAIL PROTECTED]>, Chuck Tuffli write
s:
>I've been chasing down some weird panics in my CAM driver and have
>noticed that functions don't seem to save all register values before
>they modify them.
>
>For example, function A uses register ecx to hold the value of a pointer. Part way
>
6 matches
Mail list logo
