T.R | Title | User | Personal Name | Date | Lines |
---|
3254.1 | stack is corrupted | MUCTEC::BECKER | Hartmut B., VMS & Languages, Munich | Wed Mar 05 1997 06:17 | 13 |
| I'm in contact with the partner. Their problem is a corrupted stack. This is
reproducable but the culprit can't be found. Via phone I gave some debugging
hints. Up to now we only know that "something" asynchroneously writes to the
stack and overwrites two longwords. The partner says he doesn't do anything
with asts or threads. But he uses motif and immediately after the corruption is
observed there are 4 outstanding asts.
At the moment the partner evaluates if the problem is still there with V7.1.
They can upgrade and they know of a customer running 7.1 who didn't report the
problem.
Hartmut
|
3254.2 | problem not solved but closed | MUCTEC::BECKER | Hartmut B., VMS & Languages, Munich | Tue Mar 11 1997 05:13 | 9 |
| The problem also shows up on V7.1. He also assumes that the problem is in
the GKS library they use between X and their application. It looks like
someone has to go onsite and help them debugging. It also looks like it
isn't our code which corrupts the stack.
It looks like we can't handle this within ASAP, I'm still in contact with
the partner but I close the call.
Hartmut
|
3254.3 | solved | MUCTEC::BECKER | Hartmut B., VMS & Languages, Munich | Mon May 05 1997 05:48 | 4 |
| It turned out they used an automatic variable from another c function as iosb to
a QIO with AST. This was found by a local support engineer who went onsite.
Hartmut
|