>> Can you single-step through the code? If so, step until you reach the
>>"strcpy" line and do "bytes *ptcBuffer". You can also add some EC code in
>>there to catch any bad handles or invalid pointers.
>>
>Well, it's not quite that easy :) The code that follows is..
>
> @send
optrText::MSG_VIS_TEXT_REPLACE_ALL_OPTR(@MyBuffer,VUM_DELAYED_VIA_UI_QUEUE);
Oh boy, what a fool I am! The code used to work, because I used to have
zero as the second parameter in MSG_VIS_TEXT_REPLACE_ALL_OPTR. Then I
changed it to VUM_ ...
Why did I do that? Because I didn't really know why the zero was there!
Because someone asked, why it was there and if it shouldn't be something
else.. I changed it just like that. Stupid, stupid, stupid..
After some RTFM I feel a lot better, not to mention the code works :)
Thanx Nathan, you made me _think_ about the problem. Now if only I'd do
that beforehands <sigh>
But I still don't know how to check the contents of any/some global
variable via swat without having a pointer in my code. If anyone would
ask me, I'd say that "pobj @MyBuffer" should show me what I'm asking.
>>Nathan
>
>--jouni
--jouni