X-Spam-Check-By: sourceware.org Message-ID: <45FAEE93.8080707@cwilson.fastmail.fm> Date: Fri, 16 Mar 2007 14:22:59 -0500 From: Charles Wilson User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Using cygwin1.dbg References: <45FAC9DD DOT 2050804 AT cwilson DOT fastmail DOT fm> <45FAE95C DOT CDC304AA AT dessent DOT net> In-Reply-To: <45FAE95C.CDC304AA@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brian Dessent wrote: > This is just a bug in insight. It has existed for some time. There is > code in gdb to supress these errors when loading the debug file, but > when running under insight the plumbing for messages is different and so > they get displayed. I've been meaning to look into this for quite some > time but it's just an annoyance so I never got around to it. Err, ok. But shouldn't I be able to do source-level debugging, rather than asm-only? (That is one difference between using cygwin1.dll alone, and with cygwin1.dbg: in the former case, cygwin calls are simply stepped over, even in I try to step into. In the latter case, I can step into, but I get asm not source) Hmmm--I just thought of something: do I need to replicate the source code path structure in the .dbg file: /ext/build/netrel/src/cygwin-1.5.24-2/... perhaps by using a symlink, pointing to the location that setup.exe actually unpacked cygwin-1.5.24-2-src.tar.bz2? /usr/src/cygwin-1.5.24-2/... Yep, that works. I vaguely recall something in the gdb docs about overriding src paths, so that'll probably work too if I drag out TFM and actually R it. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/