xdvik

Logged In: YES
user_id=177175

Fixed in rev.1.61 of xaw_menu.c (use globals window_w,
window_h instead of local variables - yuck ...). Will be in
next release following 22.77.

Logged In: YES
user_id=177175

More specifically, this is not a segfault, but an X error;
the error message is:

X Error of failed request: BadValue (integer parameter out
of range for operation)
Major opcode of failed request: 12 (X_ConfigureWindow)
Value in failed request: 0x0
Serial number of failed request: 5162
Current serial number in output stream: 5169

Investigation pending.

Logged In: YES
user_id=177175

> This does not happen on my Linux box.

Yes, I can't see anything suspicious with valgrind on Linux
either -
when you say it crashes, you mean a segfault, not something like
and X protocol error, right?

Does it produce a core file, could you send me a backtrace?
Or maybe run it in the debugger? (E.g. for gdb - Solaris
might have
a different debugger:

$ gdb xdvi-xaw.bin
<gdb> run test.dvi
... crash ...
<gdb> backtrace
)