On Mon, 5 Apr 2010 17:04:55 +0200
Jonas Maebe wrote:
> Unlikely. You can always disable the explicitly with -O-. Without a
> compilable example program that demonstrates the problem I cannot help
> further.
Ok... Thanks! Will try to extract the important part.
John
_
On 05 Apr 2010, at 16:36, John Coppens wrote:
> gives:
>
> 654 if ch = eofchar then
> (gdb) n
> 655 sy := sps[ch]
> (gdb)
> 659 goto 1;
> (gdb)
> 661 symbol_read := true;
>
> Does this have anything to do with optimizations?
Unlikely. You can always disable
On Mon, 5 Apr 2010 16:21:33 +0200
Jonas Maebe wrote:
> This usually means that you modified the file since it was loaded in
> the debugger.
And it still gives some strange result:
if ch = eofchar then
sy := sps[ch]
else begin
error(erchar);
nextch;
g
On 05 Apr 2010, at 16:27, John Coppens wrote:
> Doesn't gdb detect source code changes? It's been a while, but I seem to
> remember gdb warning about the C source file having been changed.
GDB warns if *on startup* the time stamp of a source file is newer than that of
the binary. If you change
On Mon, 5 Apr 2010 16:21:33 +0200
Jonas Maebe wrote:
> > I haven't seen this kind of problem before, not in Pascal nor in C.
> > Why is the '... to 1' appearing in the listing?
>
> This usually means that you modified the file since it was loaded in
> the debugger.
That was it - but it seems sl
On 05 Apr 2010, at 16:17, John Coppens wrote:
> I haven't seen this kind of problem before, not in Pascal nor in C.
> Why is the '... to 1' appearing in the listing?
This usually means that you modified the file since it was loaded in the
debugger.
Jonas___
Hi all,
When trying to debug a series of events in a program, parts of source
lines disappear - apart from the fact that the execution secuence seems
very off.
This extract from the source file:
if ch = eofchar then
sy := sps[ch]
else begin
error(erchar);
next
