home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!mcsun!news.funet.fi!funic!nntp.hut.fi!nntp!ppessi
- From: ppessi@vipunen.hut.fi (Pekka Pessi)
- Subject: GCC - How to debug a program using ixemlib?
- Message-ID: <PPESSI.92Aug18050721@vipunen.hut.fi>
- Sender: usenet@nntp.hut.fi (Usenet pseudouser id)
- Nntp-Posting-Host: vipunen.hut.fi
- Organization: Helsinki University of Technology, Finland
- Date: 18 Aug 92 05:07:21
- Lines: 19
-
-
- I have some problems trying to debug GNU GCC compiled programs
- using ixemlib. Is there some way to tell ixemlib that those
- nasty ILLEGALs are really breakpoints made by my debugger?
- Should I link with a libg.a, for instance? (Any hints how
- to get libg.a are approciated.)
-
- Currently I have patched _ixopen not to set tc_TrapCode, but
- it is quite a kluge. I have tried to RTFS but I have not found
- anything suitable.
-
- Also, what can I assume in atexit'ed function? Is stdio still
- working? Or unix compatible system calls? (I want to restore
- stdin to cooked mode and disable all RAW event reporting.) If
- I call restoring function before exit(), it works fine. If it
- is atexit()'ed, result is a meditation moment.
-
- --
- Pekka Pessi / ppessi@niksula.hut.fi
-