| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
1. Why are there two cma libraries shipped with the kit ? /usr/mcc/mmtoolkit/lib/mips_libcma.a /usr/mcc/mmtoolkit/lib/mips_libcmalib.a Which one should we link against ? 2. mcc_printf is not in that kit ? Can we use printf ? Or should we use cma_printf ? 3. With that new kit, we now encounter the following errors : %Thread 10 terminating with exception: Exception: Invalid memory address Exception: Invalid memory address IOT trap (core dumped) Any idea ? Are we missing something about io calls "jacketing" or cma ? Regards, -- Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2036.1 | Some thread answers | TOOK::MINTZ | Erik Mintz, DECmcc Development | Tue Jan 07 1992 11:50 | 31 |
>1. Why are there two cma libraries shipped with the kit ? > /usr/mcc/mmtoolkit/lib/mips_libcma.a > /usr/mcc/mmtoolkit/lib/mips_libcmalib.a > Which one should we link against ? We ship exactly the libraries that CMA provides. I think that most people only need the routines in mips_libcma.a, but we link against both. Check CMA documentation for details of what is in each. >2. mcc_printf is not in that kit ? Can we use printf ? > Or should we use cma_printf ? mcc_interface_def.h automatically re-vectors printf (and variants) to cma_printf. So you should use plain "printf" in your code. mcc_printf is obsolete. >3. With that new kit, we now encounter the following errors : > > %Thread 10 terminating with exception: > Exception: Invalid memory address > > Exception: Invalid memory address > IOT trap (core dumped) This is a rather generic error message that means something is wrong in your memory management. It could be a bad pointer, an argument mismatch on a function call, or a stack corruption problem. No easy way to tell why... -- Erik | |||||
| 2036.2 | printing is the PM domain | TOOK::CALLANDER | MCC = My Constant Companion | Wed Jan 15 1992 17:24 | 6 |
please note that no module other than the PMs should ever put a printf
in their "production" code (meaning the code path run on a production
system). The use of printfs outside of PMs can cause the PMs to get
"confused". Please beware of this and put all prints under #ifdef debug
or logical control.
| |||||