Re: Slow nasm

volcano <vkdemir@xxxxxxxxx> écrivait news:1193492104.804557.53650
@v3g2000hsg.googlegroups.com:

As i said, my complains about freezing application with bigger
circles.

Sorry for miss-understanding, then.


But not sure. I would debug if it give an error. But is
working well with 30-40 circles.

It is usually difficult to debug faults coming out during
the intialization of a DialogBox. RosAsm's Debugger also
fails to point to the faultive instruction. Two cues:

* Possible wrong return value out of the DialogProc.

* Possible unpaired Stack.

[Sorry, but i have no time for debugging your app completely]


Anyway, looked at code with olly. I saw lots of useless "00". So,
thought that the compiled code is not optimized well.

This sentence does not mean a thing.


The link In my first post, there is a Tasm code too. It is working
good.

This does not mean that your NASM port is right.


Maybe i can try on the code for a working copy. Or use masm etc. But
if nasm is wrong, this must fix. I want to give a chance to it.

You can't give a chance to NASM: NASM owe you nothing. This
was you who got a chance, and let me tell you that NASM will
agrea giving you as many chances as you will want to get.

:)

Anyway, one of the component(code,nasm,alink,nagoa.obj) is wrong.

No. You Code is wrong. Period.

First, do something clean. That is, not mixing Data right in
between Code with stupid jumps around the Data. Set your
Declarations together in a normal Section. Then re-organize
your procedure the correct standard way.

After doing this, if the app still hangs, verify your API
calls to make sure that the wanted number of parameter is
correct. If still nothing, verify the return Codes of the
DialogProc.


Betov.

< http://rosasm.org >



.