On Mon, May 2, 2011 at 10:43 PM, Eric Cooper <e...@cmu.edu> wrote: > On Mon, May 02, 2011 at 09:33:33PM +0200, Øyvind Harboe wrote: >> Perhaps you can add a polymorphism hook where the >> current behavior for handling software breakpoints >> is the default? > > If I understand what you mean by "a polymorphism hook", that would > mean adding new methods for set/unset_breakpoint, which are currently > private helper functions in arm7_9_common.c. Currently there are > methods for add/remove breakpoint, but that's not sufficient because > the resume code needs the lower-level set/unset to step over breakpoints.
I haven't studied this problem of what this design should be like. Perhaps add a set/unset software breakpoint fn's that do what they do today, but can be overridden to handle caches? Last time I worked on this, I took the shortcut of adding sw breakpoint cache handling in the type->write_buffer() hook -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
