[hatari-devel] start and break question

[Eero Tamminen]

Hi,

On maanantai 06 kesäkuu 2011, Nicolas Pomarède wrote:
> > I think catching the first program instruction would need a new virtual
> > debugger variable that tracks the OS program basepage and the text
> > segment address in that.  It would be then possible to set a
> > breakpoint on it and its changes.
> > 
> > How does that sound and how should I name that variable?
> 
> What code would you use to get the basepage on any TOS version ?

Info command should already have all the necessary checks for getting 
sysbase/basepage on different TOS version.  With the attached patch,
you can use just:
	b BasepageTextSegment > 0 && pc = BasepageTextSegment

To break on normal program startup.

Currently the variable shows a value althought there's no program running,
so I was wondering should it return zero until the text segment _size_ is
also non-zero?


On maanantai 06 kesäkuu 2011, Laurent Sallafranque wrote:
> You may call it something like debug_startAndBreakProgram or
> debug_basepagePrg, ...
> 
> (debug to know it's a debugging variable)

I think the "debug" prefix is redundant.  All breakpoint variables in
the debugger are "debugging" variables. :-)



> PS : this variable could also be used in a graphical debugger : we could
> launch a program, and if the check button "break on start" is activated,
> the debugger would break on the first instruction.
> This would be nice, no ?

Definitely. :-)


	- Eero
-------------- next part --------------
A non-text attachment was scrubbed...
Name: text-segment.diff
Type: text/x-patch
Size: 2015 bytes
Desc: not available
URL: <https://lists.berlios.de/pipermail/hatari-devel/attachments/20110606/43909648/attachment.bin>