X-Spam-Check-By: sourceware.org Message-ID: <45FAF40C.49AC16E1@dessent.net> Date: Fri, 16 Mar 2007 12:46:20 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) 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> <45FAEE93 DOT 8080707 AT cwilson DOT fastmail DOT fm> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 Charles Wilson wrote: > 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) Yes, you should, but that's orthogonal to the popup messages. > 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. Ah, that would do it. In gdb >= 6.6 there is the "set/show substitute-path" feature for this case. But unfortunately the current packaged gdb is too old to contain this. Brian -- 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/