Took a closer look and Stefano's remarks are on the mark. That field of the qpx is just the window handle and in windows it is an unsigned int so can show in J as a negative number.

Does this happen after a reboot with a clean start of J (that is, what is 1 {:: , wdforms '')? In that case there is a mystery that needs to be sorted out.

If it occurs after you have run stuff that uses enough address space so that the allocation of new windows are at unsigned addresses that appear as negative in J then the bugs in jijs need to be fixed.

----- Original Message ----- From: "Dan Bron" <[EMAIL PROTECTED]>
To: "Programming forum" <[email protected]>
Sent: Tuesday, February 06, 2007 12:09 PM
Subject: [Jprogramming] wd 'qpx'


My J IDE is broken. Whenever I try to open a new IJS window now, through File>New or File>Recent or CTRL+N or whatever, this error is raised:

|domain error: wd
|       wd'psel ',>i

and no script window appears. Debugging a bit, the fundamental problem appears to be that the window handles returned by wd'qpx' are negative. For example:

   1 {:: , wdforms ''
-1054277158

(this looks like integer overflow to me.) This started happening yesterday, and is intermittent. By intermittent, I mean that if I get this problem and close the J session and start another, the problem my disappear, but probably won't.

I did not change my J installation in any way. The problem started when J crashed on me yesterday. I think the crash was related to these big files I'm processing; J seems significantly less stable with a lot of data in memory.

After closing & restarting J a zillion times yesterday, the problem seemed gone for good. It did not recur for the remainder of the day, or this morning when I started work.

But now I just had another crash [1]. And it's back. I can't work. Can anyone help?

-Dan


[1] I don't know the specific bug that caused the crash, but the sequence of events was:

   *  Load my application script, which sets debug mode
      and pulls in large file.

   *  Application then starts processing the file, resulting
      in many large nouns in memory (some mapped).

   *  Application hit an assertion and suspended.

   *  I typed   load'somescript'  in the session,

   *  J crashed (disappeared without error or warning).

This is not the same sequence that caused the crash yesterday.

In fact, I've had many crashes recently, all triggered by different sequences. Because the situation is so complex, I am not inclined to hunt down the bug(s). But one thing all the crashes had in common was the large amount of data in memory.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to