🚀 go-pugleaf

This must surely be the single biggest screw in GDB.  It bites me at
least once a day.  I counldn't believe it wasn't fixed for 4.5.

To lose, run gdb on some file, set some breakpoints, run, recompile
the executable, use the "file" command to snag the new executable,
then type "info break".  Bye bye GDB.



Core was generated by `gdb'.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x0.
#0  0x336a4 in fputs_filtered (linebuffer=0x1<Address 0x1 out of bounds>, 
    stream=0xc1e94) at utils.c:958
958     if (stream != stdout
(gdb) bt
#0  0x336a4 in fputs_filtered (linebuffer=0x1<Address 0x1 out of bounds>, 
    stream=0xc1e94) at utils.c:958
#1  0x8a84 in breakpoint_1 (bnum=-1, allflag=0) at breakpoint.c:1059
#2  0x8bf0 in breakpoints_info (
    bnum_exp=0xffffffff<Address 0xffffffff out of bounds>, from_tty=1)
    at breakpoint.c:1110
#3  0x38c4 in execute_command (p=0xd900f "", from_tty=1) at main.c:882
#4  0x3a84 in command_loop () at main.c:943
#5  0x36c4 in main (argc=5, argv=0xf7ffefac) at main.c:820