[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::decladebug

Title:Digital Ladebug debugger
Moderator:TLE::LUCIA
Created:Fri Feb 28 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:969
Total number of notes:3959

848.0. "ladebug produces core dump, why ??" by NETRIX::"[email protected]" (Ludwig Dallmeyr) Wed Feb 19 1997 11:09

Hi,

I have a customer with a problem regarding ladebug.
Every time he tries to debug a certain file he gets a
core dump, when invoking ladebug.

He is running Digital UNIX 4.0b and ladebug version 40-25.

His object file was linked with C, C++ and fortran modules.

Used the following compiler versions:

f77 V3.8-064
cc V5.2-033
cxx V5.3-004

He sent me a stack trace of his core file:

0x1246209c
------------------
object file name: /aed405/home/AIS20/OSF1V3.2/runtime/exe/ais
Reading symbolic information ...Assertion failed: alternateEntryPointStack !=
NULL src/libsrc/ladebug/parsesymscoff.C 9104
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 ...
0x1246209c
0x1245fc04
0x1245ecf4
0x1243dc44
0x123d495c
0x124202e8
0x12395abc
0x12226350
0x122133cc
0x1220fd5c
end of diagnostic stack trace.

Ladebug Debugger Version 4.0-25 caught signal "IOT/Abort trap" (6).
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 ...
0x242f5a50
0x243a5650
0x2431db04
0x24367f44
0x2437ea6c
0x2426e074
0x2428a210
0x2428b624
0x2428b668
0x2426d64c
0x2426d788
0x123b0c5c
0x1246209c
0x1245fc04
0x1245ecf4
0x1243dc44
0x123d495c
0x124202e8
0x12395abc
0x12226350
0x122133cc
0x1220fd5c
end of diagnostic stack trace.

I have no clue what this could mean. 
Your help is greatly appreciated,

Ludwig.

CSC Munich
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
848.1TLE::MURRAYWanfang MurrayThu Feb 20 1997 12:017

Would you please have the customer try out ladebug 4.0-30?
We have put in some fixes in this area since 4.0-25.

Thanks
Wanfang
848.2TLE::LUCIAhttp://asaab.zko.dec.com/~lucia/biography.htmlThu Feb 20 1997 12:0213
Generally, this means that there is unsupported compiled code somewhere in the
image.  Versions of Fortran-77 prior to 3.6 did not correctly output alternate
entry point information.  This caused ladebug to produce this behavior.

Please make sure that ALL fortran code, including all libraries that contain
fortran code, are compiled with -g and with F77 3.6 or later.  If the problem
still persists, we will need to have the binary to reproduce the behavior.  The
sources may or may not be necessary, depending on what we find.

Any chance there is assembler code in here some place?

Regards,
Tim