matthew green <mrg@eterna.com.au> writes:

> some more points i've discovered:
> 
> 
> 	- if i attach to an already running process, i can set breakpoints
> 	quite happily and they work.

hmm.

> 
> 	- on the sparc, the calls to write target memory come _after_ the
> 	call to "run".  eg, if you do "break main", some things are setup,
> 	but the target memory isn't actually modified until "run".  on
> 	the alpha, there are no target memory interactions after "run"..
> 
> 
> the latter makes sense -- you can't write target memory until the process
> is actually running.  to it seems that this functionality is missing for
> the alpha...

This is normal on all platforms I've looked at; if you fire up gdb on
something, it just records the breakpoints as internal state until you
run the program.

I have no idea why that would even be machine-dependant.

        - Nathan