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/
