Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Sun, 9 May 1999 11:20:51 -0400
From: Chris Faylor <cgf AT cygnus DOT com>
To: Egor Duda <deo AT logos-m DOT ru>
Cc: cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: new core files
Message-ID: <19990509112051.A598@cygnus.com>
References: <15662 DOT 990509 AT logos-m DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <15662.990509@logos-m.ru>; from Egor Duda on Sun, May 09, 1999 at 03:54:36PM +0400

On Sun, May 09, 1999 at 03:54:36PM +0400, Egor Duda wrote:
> The problem is to tell debug info from data segment by looking into
> process's virtual memory. The only way i know is to try to find out
> full path to dll or exe, which is mapped into given part of process's
> address space, and to extract segment info from the image. But the
> only "legal" way to do it, afaik, is to use microsoft's nt-only
> psapi.dll.

It's possible to do this by inspecting the tortuous chain of information
in memory.  There are hints of this in DejaNews but I've never seen actual
code which does this.

-chris