home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!psinntp!psinntp!ncrlnk!ncr-mpd!kentd
- From: kentd@FtCollins.NCR.com (Kent Dalton)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: GCC - How to debug a program using ixemlib?
- Message-ID: <KENTD.92Aug18140500@zappa.FtCollins.NCR.com>
- Date: 18 Aug 92 13:05:00 GMT
- References: <PPESSI.92Aug18050721@vipunen.hut.fi>
- <1992Aug18.130108.2023@bernina.ethz.ch>
- Sender: uucp@ncr-mpd.FtCollins.NCR.COM
- Organization: NCR Microelectronics, Ft. Collins, CO
- Lines: 27
- In-reply-to: wild@nessie.cs.id.ethz.ch's message of 18 Aug 92 13:01:08 GMT
-
- >>>>> On 18 Aug 92 13:01:08 GMT, wild@nessie.cs.id.ethz.ch (Markus Wild) said:
-
- Markus> In article <PPESSI.92Aug18050721@vipunen.hut.fi> ppessi@vipunen.hut.fi (Pekka Pessi) writes:
- > using ixemlib. Is there some way to tell ixemlib that those
- > nasty ILLEGALs are really breakpoints made by my debugger?
-
- Markus> Hmm.. nah, the only way to have is to attach to an already
- Markus> running process. As soon as gdb can use a hunk libbfd.a, i'll
- Markus> go for ptrace(), which will enable a special SIGTRAP mode.
-
- Does this mean you're thinking about or better yet, working on, porting
- gdb? Please say yes :^). Source debugging is the only thing holding me
- back from using GCC to its (my :) fullest potential.
-
- Also, is there a new ixemlib due out anytime soon? Any neat new
- features?
-
- Just another GCC fan. :^)
-
- --
- /**************************************************************************/
- /* Kent Dalton * EMail: Kent.Dalton@FtCollinsCO.NCR.COM */
- /* NCR Microelectronics * Phone: (303) 223-5100 X-319 */
- /* 2001 Danfield Ct. MS470A * FAX: (303) 226-9556 */
- /* Fort Collins, Colorado 80525 * */
- /**************************************************************************/
- Now that I have my ``APPLE,'' I comprehend COST ACCOUNTING!!
-