Neale,
I come from a time before the GUI, back when -g *did* disable
disable optimization, a time before source-code debugging,
back in the mists of pre-history where even adb seemed like
a magical debugging facility. I guess it's not unreasonable
that source code debuggers can cope with optimized code-
nowadays. The first generations of sdb and cdb did require
unoptimized code, though.
(OK, OK, so I made the jump from @PMD and @FLIT on a
UNIVAC-1100 to various flavors of Unix/Xenix, but even @PMD
was a jump on //sysudump dd sysout=a, if you get my drift...)
Yes, we _did_ program using stone knives and bearskins.
We used the stone knives to put holes in the cards and we
tattooed the pelts with our listings...
(Yes, I've also toggled programs directly into Xerox Sigma 9s,
TI-960s, PDP-8s and the like; It's good that those days are
"mostly" gone.)
--------------------
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Adsumo ergo raptus sum
IBM Certified: IBM AIX 4.3 System Administration, System Support
"Ferguson, Neale"
<Neale.Ferguson@Software To: [EMAIL PROTECTED]
AG-USA.com> cc:
Sent by: Linux on 390 Subject: Re: [LINUX-390]
Debugger question - gdb?
Port
<[EMAIL PROTECTED]
>
08/13/2002 10:01 AM
Please respond to Linux
on 390 Port
-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.
