reilly@tel2.tel.vtt.fi (Jim Reilly - reilly%vtttel@router.funet.fi) (07/17/89)
I'm trying to use 'dbx' on our Apollo 3500 (sr10.1) and am having some problems. I'm trying to use dbx from my vt220 terminal in my office, since I can't always be able to do debugging from the system console, as other people use the console quite a lot. I can't seem to get line #'s for my C code to appear at breakpoints or when single stepping. Instead, I get hex addresses and assembly language instructions. I tried a control experiment using just a small number of C source files and dbx seemed to work just fine. It only seems to be when I use dbx to run an executable compiled from a larger number (we have 40+ "C source files" in our system - some are small, others are relatively large) of object files, that I have problems. I've tried compiling with -g on every .c that goes into the executable and also tried compiling just the ones I care about with -g. Same thing, just hex addresses and assembly code. I'm just wondering if there is some sort of size limit for dbx on the Apollo, or some option flag I should try during compiling (I also tried -dba instead of -g for the heck of it). Has anyone else experienced this ? Found a work-around ? Any other suggestions ? Thanks! Jim Reilly, Please respond to: reilly%vtttel@router.funet.fi reilly%vtttel@FINFUN.BITNET