Re: emacs debugging conundrum (success ?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Angelo Graziosi on 4/23/2006 8:12 AM: > > Eric, > > I do not know if this can help but I have experimented the following. > > > cd /tmp > rm -rf emacs/ > tar -xjvf emacs-22.0.50-cvs-src.tar.bz2 > > mkdir emacs-build > cd emacs-bu

Re: emacs debugging conundrum (success ?)

Eric, I do not know if this can help but I have experimented the following. I tried to build emacs from CVS in this way (I downloaded from CVS at Apr 23, about 02 am ): cd /tmp cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/emacs co emacs tar -cjvf emacs-22.0.50-cvs-src.tar.bz2 emacs cd

Re: emacs debugging conundrum

On Sat, Apr 22, 2006 at 03:59:48PM -0600, Eric Blake wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >Any ideas on how I should go about debugging a core dump, when the dump >doesn't occur under the debugger? Is it more likely to be a cygwin bug, >or an app bug? I am experimenting with C

emacs debugging conundrum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any ideas on how I should go about debugging a core dump, when the dump doesn't occur under the debugger? Is it more likely to be a cygwin bug, or an app bug? I am experimenting with CVS emacs, and the build process fails when it gets to this command