GDB requires software breakpoints?

[Daniel Jacobowitz]

On Tue, Jun 28, 2005 at 10:19:18AM -0400, Chad Phillips wrote:
> I took the advice of having the software breakpoint requests actually 
> set hardware breakpoints.  However, the problem of gdb insisting on 
> setting a software breakpoint at main has now been compounded by gdb 
> issueing a continue command after the software breakpoint is 
> successfully set.  It is as if gdb thinks it must break at main before 
> it can go on to do anything else.
> 
> In the following session, the target has been stopped in main before gdb 
> starts.  Then gdb attaches to the target.  A step command is then issued 
> to gdb.  The step occurs correctly, but at the end of the step, gdb sets 
> a breakpoint at main and then issues a continue command.  Any 
> suggestions for getting around this?

Not without more information; if you're going to continue working on a
GDB port, you really need to get used to debugging GDB.  Figure out why
GDB is issuing a continue command instead of another step.  Don't worry
about the breakpoint at main; it's not actually relevant.

-- 
Daniel Jacobowitz
CodeSourcery, LLC