From:	sturm AT ost1 DOT ping DOT de (Oliver Sturm)
Subject:	Re: ladybug fullscreen debugger
Date:	Wed, 31 May 95 16:47:12 MEZ
To:	djgpp AT sun DOT soe DOT clarkson DOT edu

>On Thu, 25 May 1995, Oliver Sturm wrote:
>
>> 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?
>
>  No. (Like any other programs, ENV VAR is optional.)
>
>> 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
>
>  go32 -d ladybug foo is the correct way to do it.
> 
>> 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 environment are you running under? (DPMI/VCPI, Memory, etc.) I've
>seen people having problems with this, but only if they recompiled the code.
>In your case, maybe the debugger was trying to write to a write-protected 
>file? Please send me the error messages and I'll try to figure it out.

I'm loading HIMEM and EMM386. go32 reports having found VCPI memory.
Im using 4DOS version 5.5.
>
>> 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.
>
>  Like it says in the manual, only v. 1.11m5n and 1.12m3 support this type
>of parameter passing. For all other versions of go32, use the environment
>variable instead:
>  SET LDBG=oldgo32 remote 2
>
>The switch oldgo32 is very important when using with the remote switch. 
>(In fact, it should be used all the time, since oldgo32 refers to any 
>go32 versions other than 1.11m5n & 1.12m3)
>
>> 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...
>
>  You shouldn't have to.
> 
>> 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
>> VCPI (Expanded) memory available: 1776 Kb
>> Swap space available: 21464 Kb
>
>  Please try one or more of the following:
>
>    - Use a memory manager (HIMEM.SYS + EMM386.EXE)

I'm already using those.

>    - Upgrade to go32 1.12m5 (optional)

How do I do that? I have installed all the djgpp-maintenance-releases 
up to m4, but I still have go32 maint 3.

>    - set LDBG to oldgo32

Not any difference to the numbers below.

>    - mail me any more error messages that the debugger created (if any)
>      and the stacktrace. I'll use that to see what happens.
>
So, this is what I happens: 

c:\djgpp\twk>go32 -d ladybug twk
go32 version 1.12.maint3 Copyright (C) 1994 DJ Delorie
73048+3072+1024 = 77144
432 Kb conventional, 1776 Kb expanded - 2208 Kb total RAM available
Create Symbol file twk.sym
Segmentation violation in pointer 0x00000005 at d8:9001f989
eax=00000000 ebx=90022e54 ecx=00000006 edx=9005c000 esi=00000005 edi=90034b29
ebp=9fffff54 esp=9fffff4c cs=d8 ds=48 es=48 fs=48 gs=38 ss=48 cr2=00000005
Call frame traceback EIPs:
  0x9001f989
  0x9001e306
  0x9001ac77
  0x90000c0f

c:\djgpp\twk>

My go32-env-var is as follows:

c:\djgpp\twk>set go32
2r1 driver c:/djgpp/contrib/libgrx/drivers/stdvga.grn emu c:/djgpp/bin/emu387

c:\djgpp\twk>

Well, that's all I know... Many thanks for your help, by the way ;)

Oliver


--

   Oliver Sturm   sturm AT ost1 DOT ping DOT de

- Raw text -