X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Thu, 26 Apr 2001 18:49:02 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	djgpp workers list <djgpp-workers AT delorie DOT com>
Subject:	Re: sbrk() storing the size of memory blocks
In-Reply-To:	<2561-Thu26Apr2001194132+0300-eliz@is.elta.co.il>
Message-ID:	<Pine.LNX.4.10.10104261844250.592-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 26 Apr 2001, Eli Zaretskii wrote:
> > Date: Thu, 26 Apr 2001 14:30:45 +0200 (MET DST)
> > From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>

> > A side remark: Debugging is a bit hard in this area, since gdb doesn't
> > know what the type __djgpp_memory_handle_list is. Probably because the
[...]

> I guess we could move __djgpp_memory_handle_list out of assembly, but
> are you really sure this will help?  I thought the problem was that it
> is defined in the library, which lacks sufficient debug info, not
> because it's defined in assembly.

Yes. But if it was in a C file, one could compile take that out of libc
sources, and compile it manually with debugging enabled. For comparison:
my test setup for the core dumper consisted out of _write.c, dpmiexcp.c
and the sources for __dj_movedata() and friends, all of them compiled with
full debugging turned on. And the test program itself, of course.

> You could always cast the references with the appropriate type, of
> course.  

I tried that, but for some reason I couldn't quite make out, it didn't
seem to work.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -