Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 18 Jan 2002 16:33:34 +0300 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <11999379039.20020118163334@logos-m.ru> To: Earnie Boyd CC: Robert Collins , Earnie Boyd Subject: Re: strace.active In-Reply-To: <3C482066.FD6BF18@yahoo.com> References: <3C4819B9 DOT 2058D39E AT yahoo DOT com> <08d201c1a01e$d9130550$0200a8c0 AT lifelesswks> <3C482066 DOT FD6BF18 AT yahoo DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Friday, 18 January, 2002 Earnie Boyd earnie_boyd AT yahoo DOT com wrote: EB> Robert Collins wrote: >> Look in utils/strace.cc - search for _STRACE_INTERFACE_ACTIVATE_ADDR. EB> But, strace.active isn't set in utils/strace.cc. I can see that EB> DEBUG_PROCESS is set in the CreateProcess flags for the create_child EB> function and I can imagine that this controls the strace.active value EB> but I don't see how strace.active is set in the cygwin1.dll. it's set from strace.cc just like Rob said. every cygwin application, when started, sends special debugging event, which contains an address of strace.active variable (see pinfo.cc, function set_myself ()). it looks like 'cYgFFFFFFFF 60012345'. strace catches it, decodes it and sets strace.active value via WriteProcessMemory in handle_output_debug_string (). time to write how-strace-works.txt, heh? :) Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19