No, thats not commonly the case at all. Actually, I can't recall the last
time the VPE crashed on me. Needless to say, I don't use Suns, and I do
remember that, way back when, we did have problems on Solaris - but back in
product days, we tracked everything we encountered down and fixed it. Of
course, both Solaris and OpenDX have drifted since then, so new problems
can easily arise.
I would encourage you to lend us a hand here. Download the source (from
www.research.ibm.com/dx) and build it with debugging options set. If you
can give us info like the stack trace from core dumps we can get a clue as
to whats going wrong. The ImportSpreadSheet problem ought to be easy to
track down. UI/VPE problems can be tougher, since there's X below our
code.
Greg
Joel Richardson
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: cc:
[EMAIL PROTECTED] Subject: [opendx-users] General
DX Robustness Question
son.ibm.com
09/25/2002 02:49 PM
Please respond to
opendx-users
First, I want to say what a fantastic tool I think DX is.
The breadth and depth of its features have been pretty much
boggling my mind since I started using it. It may really BE
the best thing since sliced bread.
That said, the version I'm using crashes a lot, and in
a number of different ways. I'm just wondering if this
is normal, specific to my platform, something I'm doing
wrong (the most like explanation), or what. If anyone can
help me, I'd sure appreciate it.
The particulars:
I downloaded the binary labelled
"Solaris Sparc v2.8 based on OpenDX 4.1.3" from the OpenDX
web site and installed it in the usual place (/usr/local/dx).
My workstation is a SunBlade 1000, running Solaris 8 and CDE.
The kinds of problems I'm experiencing include:
- VPE crashes a lot. I'm doing a lot of macro
development right now. Quite frequently, operations
like opening/closing a macro window or reloading
macro definitions will cause VPE to die. As a defensive
measure, I've been saving every couple of opertaions,
and quitting/restarting VPE every couple of saves.
- Mangling a macro's .net file. This only happened once,
but to a large, complicated macro.
It suddenly started producing 100s of syntax errors when
trying to load it. I looked at the file and it seemed
ok to me (not being a script expert, however). VPE would
show the modules, but none of the connections. I ended up
rewiring the network.
- ImportSpreadsheet causes Signal 11 in the executive.
This seems to be connected with categorization, because
if I don't categorize any columns, it works fine.
- Sometimes zooming in the Image window causes DX to crash
and kills my window manager along with my login shell!!
- Occasional complaints about bad reference counts.
Thanks in advance!
Joel
===============================================================
Joel Richardson, Ph.D. [EMAIL PROTECTED]
The Jackson Laboratory Phone: (207) 288-6435
600 Main Street Fax: (207) 288-6132
Bar Harbor, Maine 04609 URL:
www.informatics.jax.org
===============================================================
