Re: Timing is everything

On 30 Sep 2005 08:15:13 GMT, Betov wrote:
>
>We need such a Tool for RosAsm. It was "planed" since ages,
>but i have no idea about how to solve some problems:
>
>The idea was to add a Floating Menu Item, in RosAsm, in
>cases when the user would Right-Click upon a selected
>Block of Instructions,... proposing to... [Profile].
>(Such a Block Selection already exists for the Blocks
>Indentations. Just another branching...).
>
>Then, a small Routine would declare a Chunk of Virtual
>Memory, copy the selected _Code_ (after Compilation of
>the whole Source, of course), and execute it there, in
>the same way you are doing from your Dialog.
>
That sounds good. Being able to time already written code at every
place in the source would be great.

>Problems:
>
>1) The Code must be valid. I have no idea about how to
> make sure of this, and it seems simply impossible to
> me...
>
>2) We must ensure the RET (easy), per se, but, i also
> don't know how to ensure that it does not RET before
> the end of the Copied Chunk.
>
The only idea I get for this, is to set a breakpoint at the RET,
execute the code once, without changing the process and thread
priorities (it couldn't hang that bad in this way), and when it stops,
at the breakpoint, pop up a message box, asking the user whether it's
OK to time it.

>So, unless we would let the user (take a pure beginner
>playing with this, without knowing a thing...) jumping
>joyfully in the Debugger, without understanding that,
>from a working App, some Chunk could hang when executed
>independantly.
>
>Would you have any idea about how to make such a tool
>somewhat "Beginner friendly", that is, controlling that
>the selection can be executed in a secure way? (Refused
>when not secure)...
>
For a beginner, it will probably never be secure. :-)
.

Quantcast