| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 953.1 | Similar problem seen with C++ code | HYDRA::MODI | | Wed May 14 1997 16:42 | 106 |
| one of our software partner has also run into the similar problem
described in .0 albait with DEC C++ compiler.
Is this a known issue ? Is there a fix available ?
Thanks in advance,
Navin
===========
> gate.exe
Segmentation fault (core dumped)
> ladebug
Welcome to the Ladebug Debugger Version 4.0-35
(ladebug) load gate.exe
Reading symbolic information ...Assertion failed: matchingSym
src/libsrc/ladebug
/symbol.C 587
This is an unexpected condition and may indicate the presence of a
defect.
If you wish to report this, please include the stack trace that
follows.
Diagnostic stack trace ...
0x123a13dc
0x123a4f8c
0x1242cef8
0x1242d344
0x12453298
0x1245e278
0x1245d594
0x1245fc5c
0x1245bfac
0x124544cc
0x1244eb7c
0x1244c0ec
0x1244bbf4
0x1244b220
0x12449f68
0x12579ce4
0x1255e618
0x123a61a8
0x123a63dc
0x1237ded0
0x12234d2c
0x12238b5c
0x1237f610
0x1222345c
0x1224c51c
0x1221fad4
0x12224020
0x122142ec
0x122114a4
end of diagnostic stack trace.
Could not start process for gate.exe
No image loaded ... Recovering ...
(ladebug)
(ladebug) quit
Unaligned access pid=8753 <ladebug> va=1421008c pc=12435724 ra=124e3d1c
type=ldq
Unaligned access pid=8753 <ladebug> va=14210084 pc=124356fc ra=124e3d1c
type=ldq
Ladebug Debugger Version 4.0-35 caught signal "Segmentation fault"
(11).
This is an unexpected condition and may indicate the presence of a
defect.
If you wish to report this, please include the stack trace that
follows.
Diagnostic stack trace ...
0x12435730
0x124e3d1c
0x124e4cc4
0x124e3b1c
0x124a0fec
0x12413370
0x123811e8
0x12238b08
0x12247898
0x1221fad4
0x12224020
0x122142ec
0x122114a4
end of diagnostic stack trace.
Fatal error: Segmentation fault
Unaligned access pid=8753 <ladebug> va=1421008c pc=12435724 ra=124e3d1c
type=ldq
Unaligned access pid=8753 <ladebug> va=14210084 pc=124356fc ra=124e3d1c
type=ldq
Segmentation fault (core dumped)
> ls -l gate.exe
-rwxr-xr-x 1 guest users 180224 May 14 12:12 gate.exe*
> more /etc/motd
Digital UNIX V3.2C (Rev. 148); Thu Mar 13 16:44:42 EST 1997
Digital UNIX V3.2C Worksystem Software (Rev. 148)
> ladebug -v
Welcome to the Ladebug Debugger Version 4.0-35
> cxx -V
cxx (cxx)
DEC CXX T5.6-003 on Digital UNIX (Alpha)
|
| 953.2 | | TLE::LUCIA | http://asaab.zko.dec.com/~lucia/biography.html | Wed May 14 1997 19:56 | 4 |
| Reproducers would be most helpful, in both cases. Binaries, with sources if you
have them. It's not likely it is fixed yet, since -35 is only a few weeks old.
Tim
|
| 953.3 | Status of C++ problem. | TLE::DMURPHY | | Fri May 16 1997 17:14 | 48 |
| I was able to generate a test case from the dispatd.exe problem:
motie> more test_static.C
class bool {
public:
const static bool __false__;
const static bool __true__;
};
int main() {
bool daemonFlag;
return 0;
}
Ladebug does not get a demangled name for __true__, encodeded as
__true__4bool but does get a demangled name for __false__, encoded
as __false____4bool.
We're looking into the problem in the demangler code.
If I alter the data member names
__true__ -> _true__
__false__ -> _false__
all of my problems go away... including asking "whatis bool"
motie> more test_static2.C
class bool {
public:
const static bool _false__;
const static bool _true__;
};
int main() {
bool daemonFlag;
return 0;
Hope this helps.
Dennis
|