Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!sunic!kth.se!cyklop.nada.kth.se!news From: d88-jwa@byse.nada.kth.se (Jon W{tte) Newsgroups: comp.unix.aux Subject: Re: MacsBug under A/UX 2.0 Message-ID: Date: 18 Mar 91 18:55:44 GMT References: <119@mishima.mishima.mn.org> <12567@goofy.Apple.COM> Sender: news@nada.kth.se (Mr News) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 20 In-reply-to: ksand@Apple.COM's message of 17 Mar 91 22:30:48 GMT In article <12567@goofy.Apple.COM> ksand@Apple.COM (Kent Sandvik) writes: MacsBug don't understand COFF formats well, so usually MacsBug is used for tracing Macintosh binaries running inside the MultiFinder process. However, things are happening... Yeah ! Presently, there's _no_ way of debugging gdb compiled uinter0- using coff binaries. (gdb cores at the large amount of typedefs...) I'm holding my breath :-) Kent h+@nada.kth.se Jon W{tte -- "The IM-IV file manager chapter documents zillions of calls, all of which seem to do almost the same thing and none of which seem to do what I want them to do." -- Juri Munkki in comp.sys.mac.programmer