Page 2 of 2

Re: Oricutron memory access breakpoints

Posted: Wed Apr 02, 2014 10:30 pm
by Chema
I'm using win64 mainly and win32 sometimes. Would be nice to have a version with the memory breakpoint working. I've been hunting a bug today for nearly one hour, and that feature would have saved me a lot of time

Re: Oricutron memory access breakpoints

Posted: Thu Apr 03, 2014 9:55 am
by Godzil
Chema wrote:I'm using win64 mainly and win32 sometimes. Would be nice to have a version with the memory breakpoint working. I've been hunting a bug today for nearly one hour, and that feature would have saved me a lot of time
I have a version for Mac OS X freshly build yesterday evening... No ? ;)

Re: Oricutron memory access breakpoints

Posted: Thu Apr 03, 2014 10:51 am
by Hialmar
If no-one generates it before this evening I'll build one for you Chema.

Re: Oricutron memory access breakpoints

Posted: Thu Apr 03, 2014 10:54 am
by Chema
Thanks guys. Iss sent one windows build to me, so problem solved :)

I really need to setup my computer to build it myself, but I've been lazy in this field.

Re: Oricutron memory access breakpoints

Posted: Wed Oct 29, 2014 10:50 pm
by Dbug
Is there an official version of Oricutron for Windows out with this bugfix?
I'm trying to track a memory corruption bug, and version 1.1 does not seem to correctly stop on memory accesses.

Re: Oricutron memory access breakpoints

Posted: Thu Oct 30, 2014 12:45 am
by iss
Yesterday Hialmar uploaded the newest Windows WIP build on:
http://www.petergordon.org.uk/oricutron/
http://www.petergordon.org.uk/oricutron ... 32_WIP.zip
In this version "Oricutron memory access breakpoints" should work ok.

Re: Oricutron memory access breakpoints

Posted: Thu Oct 30, 2014 6:42 pm
by Xeron
I do intend to release 1.2 soon, but there are a couple of things I want to do first, I just haven't had time :-(

Re: Oricutron memory access breakpoints

Posted: Thu Oct 30, 2014 7:08 pm
by Dbug
At least I validated that the memory breakpoints worked in the WIP version.
I will wait until an official release to update the OSDK from 1.1 to 1.2

Would be nice to be able to specify a range of a size of memory to survey :)

Re: Oricutron memory access breakpoints

Posted: Thu Oct 30, 2014 8:59 pm
by Chema
Oops, sorry Dbug. I had the intention of sending you my WIP version (the one iss kindly sent to me) which at least included the memory break points, but I totally forgot.

Glad to see someone else came in to help. Memory break points are a vital feature, though a range would be indeed a good idea.

That and the simulation of key press/release within the debugger ;)