Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sat, 24 May 2003 16:14:47 -0400
From:	Peter Davis <pdavis AT pageflexinc DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin, mutt, Windows XP issues
Message-ID:	<20030524201447.GC4080@bitstream.com>
References:	<20030524115323 DOT GA4424 AT bitstream DOT com> <Pine DOT GSO DOT 4 DOT 44 DOT 0305241223340 DOT 26092-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version:	1.0
In-Reply-To:	<Pine.GSO.4.44.0305241223340.26092-100000@slinky.cs.nyu.edu>
User-Agent:	Mutt/1.4i

On Sat, May 24, 2003 at 12:26:13PM -0400, Igor Pechtchanski wrote:
> On Sat, 24 May 2003, Peter Davis wrote:
> 
> > On Fri, May 23, 2003 at 04:39:01PM -0400, Igor Pechtchanski wrote:
> >
> > [snip]
> >
> > > > Thanks, Igor.  This was helpful, but I haven't solved these problems
> > > > yet.  Any debugging tips?  I've been able to build mutt 1.5.4, but I
> > > > don't know how to build a debug version, and, unlike 1.4i, it crashes
> > > > on some messages.
> > >
> > > See suggestion above (write a short test case that uses the same code, and
> > > keep adding code from mutt to it until it stops working).  I doubt the
> > > part of mutt that checks the mailbox timestamps has anything to do with
> > > curses.
> >
> > No, I know the timestamps have nothing to do with curses, I'm just
> > wondering if I can debug in the same window where curses is repainting
> > the screen, etc.
> >
> > Thanks!
> > -pd
> 
> Peter,
> 
> FYI, if you debug an app in gdb, it will open a new console window in
> which the app itself would run, so you won't be debugging and running the
> app in the same window.  Simply set the breakpoint in the function that
> checks the timestamps, use mutt normally, and when it stops at the
> breakpoint, step through the code (you'll still need a debug version of
> mutt, though).

Well, I figured out how to build a debug mutt.  I just had to:

    ./configure --enable-debug

When I run from a bash shell, mutt *does* overwrite the same window,
making debugging difficult.

When I run gdb from in XEmacs, with source stepping, etc., it opens a
separate window which immediately exits.  It fails on a call to
initscr(), which may be a curses thing as far as I know.  I groping in
the dark here, since I haven't debugged a program on *nix in over a
decade, and Cygwin's not quite *nix anyway.  (Hey, that could be
another FSF project ... cnq*)

Thanks.  I'll keep stumbling around this.

-pd




-- 
--------
    Peter Davis                               Pageflex Inc
    617-520-8345                          215 First Street
    617-868-0784 (FAX)                 Cambridge, MA 02142
    pdavis AT pageflexinc DOT com      http://www.pageflexinc.com

--
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/

- Raw text -