From:	j DOT aldrich6 AT genie DOT com
Message-Id:	<199607232316.AA190923810@relay1.geis.com>
Date:	Tue, 23 Jul 96 22:57:00 UTC 0000
To:	eliz AT is DOT elta DOT co DOT il
Cc:	079519 AT bud DOT cc DOT swin DOT edu DOT au, djgpp AT delorie DOT com
Mime-Version:	1.0
Subject:	Re: Please help me

Reply to message 4755805    from ELIZ AT IS DOT ELTA. on 07/23/96  3:19AM


>> seems to work fine but when I use smaller blocks, the program has a sigsev
>> thingy and dies (under DOS and CWSDPMI, but not WIndows).  This is not realy
a
>
>This is all explained in the FAQ (v2/faq201b.zip).  Section 15.4-15.5
>explain the Windows peculiarities, and section 6.4 explains the problem
>with a lot of small allocations when using CWSDPMI.

Yes, and I'd also like to mention for the record (although the FAQ covers
this too) that the new version of cwsdpmi (csdpmi2b.zip) solves this
problem by allowing you to set the size of its internal heap with cwsparam.

>To step through your program you need to set a breakpoint at the entry
>point to your `main' function, then run it, and when it hits the
>breakpoint, start stepping:
>[snip]

I asked about this a while back and never got an answer:  Why doesn't
setting a breakpoint from within a program via
__dpmi_set_debug_watchpoint() work properly with gdb?  I tried
this with a program that desperately needed to be able to dynamically
set breakpoints within itself for debugging purposes, but it never
seemed to affect gdb in any way.  I even examined the DPMI 0.9 spec
minutely to see what I was doing wrong, but to no avail.  Does gdb
support this feature?

John

- Raw text -