[AVaRICE-user] [ avarice-Feature Requests-1573793 ] Software Breakpoint Support

[SourceForge.net <no...@so...>]

Feature Requests item #1573793, was opened at 2006-10-09 08:49
Message generated for change (Comment added) made by arcanum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=425410&aid=1573793&group_id=39505

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Colin O'Flynn (c_oflynn)
Assigned to: Colin O'Flynn (c_oflynn)
Summary: Software Breakpoint Support

Initial Comment:
Software breakpoint support has been missing from
avarice due to the way breakpoints are handled.

I'm attempting to add them, which changes the
breakpoint handling a bit.


----------------------------------------------------------------------

>Comment By: Eric Weddington (arcanum)
Date: 2006-11-21 14:27

Message:
Logged In: YES 
user_id=543419
Originator: NO

Moving this to the Feature Request trackers as this is not really a bug.

----------------------------------------------------------------------

Comment By: Colin O'Flynn (c_oflynn)
Date: 2006-10-11 05:01

Message:
Logged In: YES 
user_id=579053

PS: I still ignore the single-step breakpoint as I don't
understand what the current code is doing.

In the old jtag2bp.cc, lines 442 in this if statement:

            if (slot == 0)
            {
                haveHiddenBreakpoint = true;
                .......BUNCH MORE LINES
            }

It's in there that I don't know how to implement as I'm not
sure what it's doing...


----------------------------------------------------------------------

Comment By: Colin O'Flynn (c_oflynn)
Date: 2006-10-11 04:59

Message:
Logged In: YES 
user_id=579053

Attached new file (bp_20061011_8am.tar.gz) is latest work.

Includes checking if you are using a Mega128 and limiting
breakpoints to a safe number. Data watchpoints seem to work
to some degree. Range data breakpoints untested.

I think the current code won't shuffle already set code
breakpoints around to make room for data breakpoints. This
is something still to do (I wrote it here so I don't forget!).

----------------------------------------------------------------------

Comment By: Colin O'Flynn (c_oflynn)
Date: 2006-10-09 08:55

Message:
Logged In: YES 
user_id=579053

Attached file is first stab at this. Software code
breakpoints *should* work 100%.

Need to fix some stuff, including the single-step breakpoint
which I ignore right now.

Data breakpoints are probably broken...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=425410&aid=1573793&group_id=39505