| 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 |
The following is very serious for us, because it drastically affects the
way we are allowed to structure our source pool.
/Bevin
% cat eg016.cxx
#include "eg016.hxx"
type_S x;
int main()
{
return f(&x);
}
% cat eg016.hxx
typedef struct S {
int i;
} type_S;
int f(type_S *x)
{
return x->i;
}
% cxx -g eg016.cxx
% ladebug a.out
Welcome to the Ladebug Debugger Version 4.0-29
------------------
object file name: a.out
Reading symbolic information ...done
(ladebug) stop in f
[#1: stop in int f(type_S*) ]
(ladebug) run
[1] stopped at [int f(type_S*):8 0x120002144]
8 return x->i;
(ladebug) stop at 8
Warning: More than one file named 'eg016.hxx' found in the binary.
Warning: Breakpoint not set
(ladebug) quit
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 811.1 | ADA9X::BRETT | Tue Feb 04 1997 15:49 | 5 | ||
dxladebug 4.0-29
No breakpoint buttons appear in the source for f(){...}
| |||||
| 811.2 | TLE::BRETT | Fri Apr 04 1997 14:59 | 4 | ||
fixed for C++ with CXX 5.6, Ladebug 4.0-BL34 by having GEM put out suffixed file names but still a problem for C and other languages. | |||||