I use this script and it ran clean.
gsegssti=: 6 5 4
creg=: 8 2 $ 2 4 4 4 4 0 2 0 2 2 0 2 0 4 2 4
smoutput gsegssti; creg
smoutput ($ gsegssti); $ creg
smoutput bdysegs=: 2 ]/\ (|.`]`] @. (1+ * gsegssti) gsegssti){ creg
smoutput bdysegs=: 2 ]/\ (|.`]`] @. (1+ * gsegssti) gsegssti){ creg
I suspect if you run this script, it will also run clean. If not, this
should establish a positive test.
Are those really integer? Were your gsegssti or creg memory mapped or coerced
from some pointers via external dll?
Срд, 27 Апр 2011, Arthur Anger писал(а):
> OnTue, 26 Apr 2011 10:34:33 -0400, Raul Miller <[email protected]> wrote:
> . . .
> Without the full definitions of the names you are using (and that
> probably includes the rank of cdir), we cannot hope to attempt to
> reproduce this issue.
> ------------
> Here is a slightly simpler example, with fuller detail. It appears that each
> store of bdysegs is getting corrupted.
>
> gsegssti; creg
> +-----+---+
> |6 5 4|2 4|
> | |4 4|
> | |4 0|
> | |2 0|
> | |2 2|
> | |0 2|
> | |0 4|
> | |2 4|
> +-----+---+
> ($ gsegssti); $ creg
> +-+---+
> |3|8 2|
> +-+---+
> ] bdysegs=: 2 ]/\ (|.`]`] @. (1+ * gsegssti) gsegssti){ creg
> 0 2
> 2 2
> bdysegs
> 10850952 0
> 0 0
> bdysegs
> 10850952 0
> 0 0
> ] bdysegs=: 2 ]/\ (|.`]`] @. (1+ * gsegssti) gsegssti){ creg
> 0 2
> 2 2
> bdysegs
> 10875272 0
> 0 0
>
> --Art Anger
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
