www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/04/27/11:16:12

From: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
To: DJGPP AT sun DOT soe DOT clarkson DOT edu
Date: Thu, 27 Apr 1995 13:32:10 BST
Subject: Ladybug

  I have just had my first go with Ladybug.
  (0) DJGPP\GO32\FS\MANUAL (Ladybug manual) contains no section "how to <run>
Ladybug". I found the missing matter as section 4 of DJGPP\GO32\FS\README
(Ladybug readme), which has a mistake in it. It recommends one of these four
call lines:-
      go32 -d edebug32 app [args ...]
      go32 -d ed32-dpm app [args ...]
      go32 -d edebug32 [-com_num] app [args ...]
      go32 -d ed32-dpm [-com_num] app [args ...]
  But `edebug32' hereinabove should read `ladybug'. I created a file
DJGPP\BIN\LADYBUG.BAT containing the line
      go32 -d ladybug %1 %2 %3 %4 %5 %6 %7 %8
  and typing `LADYBUG A.OUT' now duly calls Ladybug on the program stated.

  (1) In Ladybug, across the top of the screen is a menu header line like in
Word Perfect and Quattro Pro etc. How do I select an entry from that menu?
When I enter Ladybug, no mouse cursor appears; DJGPP\GO32\FS\MANUAL says
nothing; various experimental key strokes did nothing to or with this menu.

  (2) If I run a program under Ladybug, and it halts or fails, how do I find
the source program and the Gnu C variable values at the moment of failure? The
CODE window only displays assembler code.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019