On Jan 30, 2005, at 8:15 PM, Markian Hlynka wrote:
On Jan 30, 2005, at 12:23, Chris Espinosa wrote:
On Jan 30, 2005, at 11:16 AM, Michael de Haan wrote:
The reason I am unable to view "e" in the debugger is because it has only been declared and not initialized?
Or is there a setting I am missing.
'e' doesn't exist. Since it's never assigned nor used, the compiler hasn't even allocated space for it to be stored. There's no information in your compiled code about where 'e' should be, so the debugger cannot show it.
shouldn't compiling with -g force e to exist?
No. In fact the gcc man page says, pretty explicitly:
"GCC allows you to use -g with -O. The shortcuts taken by optimized code may occasionally produce surprising results: some variables you declared may not exist at all; flow of control may briefly move where you did not expect it; some statements may not be executed because they compute constant results or their values were already at hand; some statements may execute in different places because they were moved out of loops."
-g sets the type and level of debugging information, but doesn't force the compiler to do things it ordinarily wouldn't in code generation.
Chris
|
