On 29 April 2014 22:51, Markus Fritsche <mfritsche@reauktion.de> wrote:

Hello Igor,

> Also, i doubt it, but try change the alignment
> NativeBoostWin32>>stackAlignment
> ��to use 16

That did the trick - it was ^ 1 - changed it to ^ 16 and now the DoIt
opens an inspector on a TM1P object.

��

This is weird..

��

Can you try one thing:

change:

NBFFICallout>>foreignCall: aBlock

�� callInfo := self newCallInfo.
�� callInfo alignment: 16.
�� asm performingCall: callInfo in: aBlock.

while use:

NativeBoostWin32>>stackAlignment

�� ^ 1

and then swap values. And tell which case works and which is not (they both may not work though). Don't forget to restart image before trying to reset all generated code.

��

(you can also use #optNoAlignment option while calling external function e.g.

self nbcall: blah options: #(+optNoAlignment).

I wanna know, who corrupts stack: external function or VM itself.

Should this be reported on fogbugz?

Thank you
�� Markus

--
Best regards,
Igor Stasenko.