| Title: | LSM |
| Moderator: | SMURF::SHIDERLY |
| Created: | Mon Jan 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 803 |
| Total number of notes: | 2852 |
A customer has 2 machines in an ASE cluster. up until a few weeks
ago dxlsm ran fine on both machines (neither with Xconsole so he
sets his display back to another workstation from both of them).
Now, one of the machine core dumps whenever he starts dxlsm
The copywrite window comes up and then it segmentation faults
and core dumps.
He has moved the services off the machine and to the other and
it still happens. Commands like volprint work find and everything
is up and runnign like normal..
Is there anyway I could get a non-stripped version of dxlsm so
that we can debug this, or where I could send the core.? he is
running 3.2g, which was an upgrade from 3.2c, so the dxlsm is
from the 3.2c subsets (the same is true on our lab machines here)
Is there some other way to debug this. I have pretty much ruled
out X since other apps such as dxadvfs work fine and the other
machien works fine displaying to here. But anything is possible.
thanks
sandy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 748.1 | elevate? | RHETT::LACORTI | Fri Jan 31 1997 13:14 | 4 | |
Do I need to ipmt to get a non stripped version or have someone look
at the core?
Sandy
| |||||
| 748.2 | I guess ipmt is the only way to go.... | RHETT::LACORTI | Tue Feb 04 1997 12:14 | 5 | |
I guess I have to ipmt to get sources or a non stripped version.
oh well, i was hoping that using notes would make it quicker
sandy
| |||||
| 748.3 | I am sorry that I have not been responsive | DECWET::WALLULIS | Fri Feb 07 1997 10:14 | 23 | |
Sandy, My name is Mike Wallulis. I am the lead engineer on dxlsm. I don't normally read this notefile, but was sent mail as to your problem this morning. I have made a debuggable dxlsm for you to try, so we can produce a meaningful core. Can you tell me a bit of history about the machine? Was it right after the upgrade to 3.2g that it stopped working? Was there anything else that happened that could have affected dxlsm's operation? For this problem, please send me email at [email protected]. Let me know where you would like me to put the debuggable dxlsm for you to copy over. When this is resolved I will put the answer in the notefile here. Thanks Mike Wallulis [email protected] DTN 548-8579 | |||||