From: sturm AT ost1 DOT ping DOT de (Oliver Sturm) Subject: ladybug fullscreen debugger Date: Thu, 25 May 95 11:55:52 MEZ To: djgpp AT sun DOT soe DOT clarkson DOT edu Hi all... I have some problems concerning the ladybug debugger. I got version 1.02 from oak.oakland.edu, unzipped it and followed the installation instructions. But there are several unclear aspects in the manual and readme. The first thing is the LDBG-environment-variable. Do I have to set this if I like all the default-values? Second is the way to use the debugger. In the readme it says I should call `go32 -d edebug32 foo', where foo is my program. This doesn't work for me, which I find quite obvious, as edebug32 is a different program from ladybug and I wasn't told to rename any of them. ;) In the manual, on the contrary, it says (in the paragraph about new features) I should use `go32 -d ladybug foo', which doesn't work as well. The debugger is obviously started, but crashes after (or still within?) creating the sym-file. This happens with any program I tried, from a five-line-hello-world to a some hundred KB project. What's more, the mentioned command-line-switch for remote debugging is never recognized, whether I call it `-2' for COM2 (as it says in the readme) or `-com_two' for COM2 (as it says in the manual). The only message I always get is that the file `-2' (or `-com_two', respectively) can't be opened. I haven't tried rebuilding ladybug yet, because I suspect that to be kind of a lengthy process, but it shouldn't be necessary anyway... Alright, one word about my configuration: 486SX/25, 4 meg RAM, 120MB HD djgpp 1.12 maint4 go32 usually reports about this: go32 version 1.12.maint3 Copyright (C) 1994 DL Delorie Lowest version I can run is 1.08 go32.exe usage: go32 [-d {debugger}] [{program} [{options} . . . ]] go32.exe build time was Sun Dec 18 16:36:42 1994 XMS memory available: 1772 Kb Swap space available: 23816 Kb Thanks in advance for any answers I will (hopefully) get... Oliver -- Oliver Sturm sturm AT ost1 DOT ping DOT de