On Tue, 13 Aug 2002 21:55, you wrote:
> Many years ago I had a similar problem. Not with Linux, but running DOS on
> a PC. The problem turned out to be that the compiler thought it was
> smarter
> than me and "optimized" the code out of existance. Once I turned of
> optimization, the problem we
John Campbell <[EMAIL PROTECTED]> writes:
>
>
>
> Many years ago I had a similar problem. Not with Linux, but running DOS on
> a PC. The problem turned out to be that the compiler thought it was
> smarter
> than me and "optimized" the code out of existance. Once I turned of
> optimizat
"Ferguson, Neale"
cc:
Sent by: Linux on 390 Subject: Re: [LINUX-390]
Debugger question - gdb?
Port
<[EMAIL PROTECTED]
>
-g doesn't disable optimization.
> I would not expect a problem like this under GCC however; The act
> of using a -g is intended to disable any and all optimization.
Many years ago I had a similar problem. Not with Linux, but running DOS on
a PC. The problem turned out to be that the compiler thought it was
smarter
than me and "optimized" the code out of existance. Once I turned of
optimization, the problem went away. The program was small so it
it didn't
matter to me.
-Original Message-
From: Ann Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 13, 2002 9:04 AM
To: [EMAIL PROTECTED]
Subject: Debugger question - gdb?
One of my coworkers is having a problem debugging a C program using gdb.
For some reason it se
One of my coworkers is having a problem debugging a C program using gdb.
For some reason it seems to skip the instruction following an IF
statement. At first he thought maybe it was a bug in the debugger since
we are still using SUSE 7.0, but he tried debugging the program on a PC
running SUSE 7.
