Re: RFC: don't set the pspace on ordinary breakpoints

Jan Kratochvil
2011-10-31T00:34:42Z

On Thu, 27 Oct 2011 17:20:38 +0200, Tom Tromey wrote:
> Built and regtested on x86-64 F15, but only when applied on top of the
> previous patch.

While I find the patch OK I have a regression on
{x86_64,x86_64-m32,i686}-fedora16pre-linux-gnu:

run^M
Starting program: gdb/testsuite.unix.-m64/gdb.multi/bkpt-multi-exec ^M
+Error in re-setting breakpoint 1: No source file named crashme.c.^M
foll-exec is about to execl(crashme)...^M
-process 30058 is executing new program: gdb/testsuite.unix.-m64/gdb.multi/crashme^M
+process 13203 is executing new program: gdb/testsuite.unix.-m64/gdb.multi/crashme^M
+Oh no, a bug!^M
^M
-Breakpoint 1, main (argc=1, argv=0x7fffffffe1d8) at gdb/testsuite/gdb.multi/crashme.c:9^M
-9 printf ("Oh no, a bug!\n"); /* set breakpoint here */^M
-(gdb) PASS: gdb.multi/bkpt-multi-exec.exp: run
+Program received signal SIGSEGV, Segmentation fault.^M
+0x0000000000400519 in main (argc=1, argv=0x7fffffffe1b8) at gdb/testsuite/gdb.multi/crashme.c:11^M
+11 return *foo;^M
+(gdb) FAIL: gdb.multi/bkpt-multi-exec.exp: run

BTW the term "ordinary breakpoint" could be defined somewhere but it is
already used in FSF GDB HEAD.

Thanks,
Jan