Thanks David and Nathan for the clarification.
I was really just curious what it was used for. I assumed the “FP”
referred to frame pointer but didn’t know for sure what “O” stood for.
It was one of those things you see often and wonder what it means.
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, May 06, 2002 2:15 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: PFO
FYI, FPO is a compiler function call optimization.
You shouldn’t need to worry about it unless you are trying to do
something like walk a stack without symbols.
-----Original Message-----
From: David Holcomb
Sent: Monday, May 06, 2002 10:04 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: PFO
FPO is “frame pointer omission”. There are a few references to it in
the debugger docs (see kv) and there are references on MSDN as well.
-----Original Message-----
From: Kelley, Jerry [mailto:xxxxx@nsisoftware.com]
Sent: Monday, May 06, 2002 6:57 AM
To: Kernel Debugging Interest List
Subject: [windbg] PFO
What is PFO that shows up in some frames on a stack dump? It appears on
some frames and I’ve been trying to determine exactly what it is and
what I’d use it for. I have a “feeling” about what it means but I’m just
not sure. It’s not documented in the Windbg help.
jerry
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to windbg as: xxxxx@nsisoftware.com To
unsubscribe send a blank email to %%email.unsub%%