Re: Inferior process receives SIGSEGV on invalid breakpoint

[Michael Elizabeth Chastain]

Hi Xavier,

> The inferior process receives SIGSEGV when stopping at a breakpoint
> set at an invalid program instruction address.

Thanks, but this is not a bug.

Like most debuggers, gdb implements breakpoints by writing a
breakpoint instruction on top of the original instruction.
In your test case, "break *0x804871" explicitly writes the
breakpoint opcode into the *middle* of an existing instruction.
That changes the existing instruction to some bizarre unspecified
instruction.

(I have your other reports here, and I'll get to them when I can,
but I can reply to this one easily.  The reports are very nice.
Just one thing -- can you upgrade from gdb 5.3 to gdb 6.0?  Thanks.)

Michael C
GDB QA Guy