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
> optimization, the problem went away. The program was small so it didn't
> matter to me.
> <<<<<<<
>
> 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.
That's not the complete story - in GCC you can specify -O and -g at
the same time.
Thus, you can have an optimized program that contains some debugging
information.
This may be easier to understand if we could see a glimpse of the
source...
Also - we have discovered some issues with the 390 and 'z'
versions of gdb, and made several fixes. These have been returned
back to the official gdb tree, and should show up in future
versions.
- Dave Rivers -
--
[EMAIL PROTECTED] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
