| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2066.1 | problems with pthread$rtl | CSC32::J_HENSON | Don't get even, get ahead! | Fri Jan 17 1997 16:50 | 13 |
| 2066.2 | ??? | CSC32::J_HENSON | Don't get even, get ahead! | Wed Jan 22 1997 09:56 | 4 |
| 2066.3 | ? | CSC32::J_HENSON | Don't get even, get ahead! | Mon Jan 27 1997 12:38 | 8 |
| I don't mean to be pushy, but I really would like some feedback on this.
I think that this is a serious issue, and deserves some investigation.
If it's already being worked, would you let me know? If not, do I
need to QAR or submit an IPMT case for this?
Please advise,
Jerry
|
| 2066.4 | QAR (internal) or IPMT (external) problems... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Jan 27 1997 12:47 | 1 |
|
|
| 2066.5 | Investigating as CRTL report number 1664 | TLE::D_SMITH | Duane Smith -- DEC C RTL | Mon Jan 27 1997 13:14 | 1 |
|
|
| 2066.6 | Thanks | CSC32::J_HENSON | Don't get even, get ahead! | Mon Jan 27 1997 14:00 | 6 |
| >> <<< Note 2066.5 by TLE::D_SMITH "Duane Smith -- DEC C RTL" >>>
>> -< Investigating as CRTL report number 1664 >-
Thanks, Duane. I just needed to know that it was being worked.
Jerry
|
| 2066.7 | | TLE::D_SMITH | Duane Smith -- DEC C RTL | Mon Jan 27 1997 14:38 | 5 |
| Webb's analysis done in CMA 1348 appears to be right on the money (as
usual). I do not want to jump in with a quick fix without a more
thorough investigation of the problem.
Duane
|
| 2066.8 | | TLE::D_SMITH | Duane Smith -- DEC C RTL | Wed Apr 02 1997 10:45 | 7 |
| Further investigation of this problem shows that the problem is caused
by communicating "thread specific" data between the setitimer()
function and the AST routine setup to fire and reset the timer.
I cannot think of a way to workaround this problem short of not linking
directly against the CMA library (which causes MULTITHREAD to be the
default reentrancy mode).
|
| 2066.9 | | TLE::D_SMITH | Duane Smith -- DEC C RTL | Mon Apr 07 1997 08:19 | 5 |
| A fix for this problem has just been checked in for the release of
OpenVMS after V7.1. It will be included in the next round of ECO kits
for OpenVMS V7.0 and V7.1.
Duane
|