Answers Database
Design Manager M1/2.1i: GUI does not start/come up under Solaris 2.5.x/2.6/2.7
Record #3306
Product Family: Software
Product Line: M1 Graphical/General
Product Part: Design Manager
Product Version: 2.1i
Problem Title:
Design Manager M1/2.1i: GUI does not start/come up under Solaris 2.5.x/2.6/2.7
Problem Description:
Urgency: Hot
General Description:
Possible solutions to why the Design Manager may not start
properly when invoked under the Solaris 2.5.x, 2.6, or 2.7 OS.
Solution 1:
In you are using Solaris 2.7 (Solaris 7) and you receive:
Segmentation fault (core dumped)
upon invoking the Design Manager (or in attempting
to invoke any other GUI application), chances are that
you need to unset the following environment variable
as follows:
unsetenv LD_BREADTH 1
This solution is likely required if the "LD_BREADTH"
variable had been previously set in order to resolve the bug
in the dynamic linker provided by Sun Microsystems with
Solaris 2.5.x/2.6.
For additional debugging hints (or if the above does not apply),
please reference (Xilinx Solution 1997)
Solution 2:
In the event that the Design Manager does not start under
either Solaris 2.5.x or 2.6, and you have already checked
the environment variables, try setting the following:
setenv LD_BREADTH 1
This forces the dynamic linker to revert to a previous mode
of operation, which is compatible with the Xilinx GUIs. This
solution is a result of a bug in the dynamic linker provided
by Sun Microsystems with Solaris 2.5.x/2.6
NOTE: Attempting to run 2.1i software on Solaris 2.5.x results
in a core dump. 2.1i only supports the Solaris 2.6 and 2.7
platforms.
End of Record #3306 - Last Modified: 07/20/99 18:08 |
