1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
**************************
* How to Report Bugs *
**************************
Email bug reports to llnlxdir@llnl.gov. Please report compiler-generated
warning errors as well as run-time errors. In addition to the particulars
of the problem, please specify:
o LLNL XDIR version number
o System (e.g., SGI IRIX 4.0.5)
o Compiler (e.g., gcc) and options
o Versions of Motif and X11
******************
* Known Bugs *
******************
o LLNL XDIR sometimes has trouble dealing with entry names that contain
embedded spaces. The symptom is that XDIR will behave as though the
entry name consists of only the last blank-delimited part of the name.
This problem occurs most frequently in the Full Info Layout mode. So,
as a workaround, try switching to another layout mode.
o Recursive file transfers to a Windows system running the WFTPD daemon
will encounter problems if the name of any transferred directory
contains more than eight characters.
o If LLNL XDIR is built with SOCKS, the STOP button will have no effect
while connecting to a remote host.
o On Solaris 2.4 systems, Xdir binaries built with Motif libraries that
were not supplied by Sun Microsystems have been known to die during
certain operations in the function _XmIEndUpdate(). The segmentation
fault seems to be due to a Motif bug, but this has not been confirmed.
The problem has not been observed with binaries built with the Motif
supplied by Sun Microsystems.
o LLNL XDIR might not behave as desired if you attempt to recursively
transfer or delete a directory that is not tree-like (that is, which
contains links that create loops in the file system).
o Although the cache mechanism is fairly reliable, it is possible to
contrive cases involving the move or recursive copy operations in
which the cache can get out of sync with the actual directory
structure.
o ********** ATTENTION LINUX USERS **********
Three bugs can occur with LLNL XDIR binaries built with Motif 2.0 on
a some Linux systems. These bugs all probably stem from the same
underlying cause, (a bad X/Motif library?, some environment variable
setting?, some X/Motif resource setting?, a bad Imake config file?),
but this is not certain. At any rate, odds are good that if you
encounter one of these bugs, it will go away if you rebuild Xdir with
a different Motif distribution. I am not a Linux user, and, hence, I
am unable to directly pursue these bugs. I would appreciate any
efforts that can be made by Linux users to eradicate these bugs or
find better workarounds. (It is worth noting that these problems
have not been reported for the many other Unix platforms that Xdir
runs on.) In the meantime, I hope that someone will make a correctly
working, statically linked Xdir 2.1 binary available for those Linux
users who are affected by these bugs (this was done for Xdir 2.0,
which also had the same problem).
BUG 1: Xdir can die with a segmentation fault when closing a
directory window. The only workaround I know of is to replace the
following line in dirwin3.c,
XtDestroyWidget(dirwin->w_shell);
with
XtUnrealizeWidget(dirwin->w_shell);
This will cause the directory window to disappear upon closing and
will free resources on the X server, but will not free widget data
structures in the Xdir client (hence, the executable will act as
though it has a bad memory leak).
BUG 2: Xdir can die with a segmentation fault the second time the
built-in viewer is invoked to display the contents of a text file.
One workaround is to replace the following line in view2.c,
XtDestroyWidget(view->w_shell);
with
XtUnrealizeWidget(view->w_shell);
Again, this workaround will free resources on the X server, but will
not free widget data structures in the Xdir client. A better
workaround is to use an external viewer (rather than the built-in
one) to view text files. You can configure Xdir to use a text viewer
of your choice (for example, xemacs) by configuring the dialog popped
up when you select "Viewer Preferences" in the "Prefs" menu.
BUG 3: Xdir can die when pressing the toolbar button with the skull
and crossbones. The following output is written to the shell:
X Error of failed request: BadDrawable (invalid Pixmap or
Windowparameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x0
Serial number of failed request: 5538
Current serial number in output stream: 5637
As a workaround, use the "Close" item in the "File" menu to close a
directory window (or use the window manager to dismiss the window).
|
