gdb/339: reread.exp fails on x86-linux

[kettenis@chello.nl]

The following reply was made to PR gdb/339; it has been noted by GNATS.

From: kettenis@chello.nl
To: gdb-gnats@sources.redhat.com, jimb@redhat.com, geoffk@redhat.com
Cc:  
Subject: Re: gdb/339: reread.exp fails on x86-linux
Date: 9 Feb 2002 17:01:09 -0000

 Hmm, I can reproduce it on FreeBSD 4.4, both with FreeBSD's standard
 compiler (GCC 2.95.3) and a GCC 3.1 snapshot that's a few weeks old.
 
 It seems to be a line numbering problem.  The test expects a
 breakpoint at line number 14 after rereading, but instead it gets one
 at line number 13:
 
 Breakpoint 2 at 0x80484a0: file ../../../../src/src/gdb/testsuite/gdb.base/reread1.c, line 13.
 
 The strange thing is that after restarting the program GDB does report
 the breakpoint to be at line 14:
 
 Breakpoint 2 at 0x80484a3: file ../../../../src/src/gdb/testsuite/gdb.base/reread1.c, line 14.
 
 Note that if GDB really didn't reread the executable the breakpoint
 would be at line number 9.
 
 I have no real clue about what's wrong :-(.  Is it that GDB reads
 additional debug info upon restarting the program and therefore is
 able to more acurately describe the location of the breakpoint?
 
 Mark