* Re: Building Emacs-cvs on Cygwin (GCC summary)
@ 2006-10-30 1:22 Maks Romih
2006-10-30 19:16 ` Richard Stallman
0 siblings, 1 reply; 24+ messages in thread
From: Maks Romih @ 2006-10-30 1:22 UTC (permalink / raw)
> GCC-3.4.4-(1/2) Segment fault
>
> GCC-4.0.3 OK
> GCC-4.1.1 OK
>
> GCC-4.2-20061024(prerelease) M-x undefined
> GCC-4.3-20061022(experim.) M-x undefined
>
>
> In conclusion on Cygwin only the build with GCC-4.0.3 and > 4.1.1 seem to
> work fine.
>
> Are there people that can confirm these results?
I can confirm the 3.4.4.1., because I've also had stackdumps when I built the emacs-22.0.50 with GCC 3.4.4.1.
Then I compiled with CFLAGS=-g to see where it breaks but it doesn't break any more, so now I happily use the debug version.
Maks.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 1:22 Building Emacs-cvs on Cygwin (GCC summary) Maks Romih @ 2006-10-30 19:16 ` Richard Stallman 2006-10-30 20:31 ` Eric Hanchrow 2006-10-30 21:06 ` Eli Zaretskii 0 siblings, 2 replies; 24+ messages in thread From: Richard Stallman @ 2006-10-30 19:16 UTC (permalink / raw) Cc: emacs-devel > GCC-3.4.4-(1/2) Segment fault > > GCC-4.0.3 OK > GCC-4.1.1 OK > > GCC-4.2-20061024(prerelease) M-x undefined > GCC-4.3-20061022(experim.) M-x undefined > > > In conclusion on Cygwin only the build with GCC-4.0.3 and > 4.1.1 seem to > work fine. Let's document that people should not use GCC 3.4 on Cygwin. Where is the best place to document this? ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 19:16 ` Richard Stallman @ 2006-10-30 20:31 ` Eric Hanchrow 2006-10-30 21:05 ` Eli Zaretskii 2006-10-30 21:44 ` Jason Rumney 2006-10-30 21:06 ` Eli Zaretskii 1 sibling, 2 replies; 24+ messages in thread From: Eric Hanchrow @ 2006-10-30 20:31 UTC (permalink / raw) >>>>> "Richard" == Richard Stallman <rms@gnu.org> writes: Richard> Let's document that people should not use GCC 3.4 on Richard> Cygwin. Where is the best place to document this? I vote for nt/INSTALL -- "Hoot" has its heart in the right place, but I have been unable to locate its brain. -- Roger Ebert ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 20:31 ` Eric Hanchrow @ 2006-10-30 21:05 ` Eli Zaretskii 2006-10-30 21:26 ` Eric Hanchrow 2006-10-30 21:44 ` Jason Rumney 1 sibling, 1 reply; 24+ messages in thread From: Eli Zaretskii @ 2006-10-30 21:05 UTC (permalink / raw) Cc: emacs-devel > From: Eric Hanchrow <offby1@blarg.net> > Date: Mon, 30 Oct 2006 12:31:53 -0800 > > >>>>> "Richard" == Richard Stallman <rms@gnu.org> writes: > > Richard> Let's document that people should not use GCC 3.4 on > Richard> Cygwin. Where is the best place to document this? > > I vote for nt/INSTALL No, that's the wrong file: the problem is in the Cygwin build, which doesn't use any of the stuff in nt/. The right place is etc/PROBLEMS. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 21:05 ` Eli Zaretskii @ 2006-10-30 21:26 ` Eric Hanchrow 0 siblings, 0 replies; 24+ messages in thread From: Eric Hanchrow @ 2006-10-30 21:26 UTC (permalink / raw) Cc: emacs-devel >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes: Eli> No, that's the wrong file: the problem is in the Cygwin Eli> build, which doesn't use any of the stuff in nt/. You're right. Eli> The right place is etc/PROBLEMS. This, however, I have doubts about: 3.4 appears to be what Cygwin installs by default, so presumably this problem will hit most Cygwin users. I think if the note were in INSTALL, people would be more likely to see it. Regardless, I think the INSTALL file could be improved a smidgen, with this change: --- INSTALL 26 Jul 2006 19:19:06 -0700 1.115 +++ INSTALL 30 Oct 2006 13:25:59 -0800 @@ -200,7 +200,7 @@ DETAILED BUILDING AND INSTALLATION: -(This is for a Unix or Unix-like system. For MS-DOS and Windows 3.X, +(This is for a Unix or Unix-like system, including Cygwin. For MS-DOS and Windows 3.X, see below; search for MSDOG. For Windows 9X, Windows ME, Windows NT, and Windows 2000, see the file nt/INSTALL. For the Mac, see the file mac/INSTALL.) -- Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. -- John F. Woods ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 20:31 ` Eric Hanchrow 2006-10-30 21:05 ` Eli Zaretskii @ 2006-10-30 21:44 ` Jason Rumney 2006-11-05 10:52 ` Jari Aalto 1 sibling, 1 reply; 24+ messages in thread From: Jason Rumney @ 2006-10-30 21:44 UTC (permalink / raw) Cc: emacs-devel Eric Hanchrow wrote: > Richard> Let's document that people should not use GCC 3.4 on > Richard> Cygwin. Where is the best place to document this? > > I vote for nt/INSTALL > That is the wrong place for instructions for the Cygwin build. The Cygwin build does not use the windows specific files in the nt subdirectory, and people who know Cygwin would not expect it to, since Cygwin is not Windows, it is a POSIX emulation environment. etc/PROBLEMS seems more appropriate. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 21:44 ` Jason Rumney @ 2006-11-05 10:52 ` Jari Aalto 2006-11-05 11:55 ` Eli Zaretskii 0 siblings, 1 reply; 24+ messages in thread From: Jari Aalto @ 2006-11-05 10:52 UTC (permalink / raw) Jason Rumney <jasonr@gnu.org> writes: > Eric Hanchrow wrote: > > Richard> Let's document that people should not use GCC 3.4 on > > Richard> Cygwin. Where is the best place to document this? > > > > I vote for nt/INSTALL > > > > That is the wrong place for instructions for the Cygwin build. The > Cygwin build does not use the windows specific files in the nt > subdirectory, and people who know Cygwin would not expect it to, since > Cygwin is not Windows, it is a POSIX emulation environment. > > etc/PROBLEMS seems more appropriate. Woudl it be possible to use OS specific file: etc/NOTES.Cygwin Jari ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-11-05 10:52 ` Jari Aalto @ 2006-11-05 11:55 ` Eli Zaretskii 0 siblings, 0 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-05 11:55 UTC (permalink / raw) Cc: emacs-devel > From: Jari Aalto <jari.aalto@cante.net> > Date: 05 Nov 2006 12:52:16 +0200 > > > > etc/PROBLEMS seems more appropriate. In the meantime, I already added to PROBLEMS an entry about Cygwin build with GCC 3.4.4. > Woudl it be possible to use OS specific file: > > etc/NOTES.Cygwin It's possible, but why would we want to do that? There are at least several good reasons not to: . System-specific files are a pain from the user's perspective, since the users need to be told where to find instructions relevant for their platform, and there's no good place to put these instructions (obviously, those instructions cannot be in a platform-specific files). the etc/ directory is very large, so letting users look for the files on their own will make things hard on them . etc/PROBLEMS has an item in the Help menu, and searching it for "Cygwin" is trivial. Many Emacs users already know about PROBLEMS and will look there when faced with a problem. . Cygwin build is, for all practical purposes, a Posix build, so users will probably assume that general Unix issues hold for it as well, and look for instructions and other build-related material in the general files, not in some OS-specific ones. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 19:16 ` Richard Stallman 2006-10-30 20:31 ` Eric Hanchrow @ 2006-10-30 21:06 ` Eli Zaretskii 2006-11-04 12:12 ` Eli Zaretskii 1 sibling, 1 reply; 24+ messages in thread From: Eli Zaretskii @ 2006-10-30 21:06 UTC (permalink / raw) Cc: maks.romih, emacs-devel > From: Richard Stallman <rms@gnu.org> > Date: Mon, 30 Oct 2006 14:16:28 -0500 > Cc: emacs-devel@gnu.org > > > GCC-3.4.4-(1/2) Segment fault > > > > GCC-4.0.3 OK > > GCC-4.1.1 OK > > > > GCC-4.2-20061024(prerelease) M-x undefined > > GCC-4.3-20061022(experim.) M-x undefined > > > > > > In conclusion on Cygwin only the build with GCC-4.0.3 and > 4.1.1 seem to > > work fine. > > Let's document that people should not use GCC 3.4 on Cygwin. > Where is the best place to document this? I will document that in etc/PROBLEMS. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Building Emacs-cvs on Cygwin (GCC summary) 2006-10-30 21:06 ` Eli Zaretskii @ 2006-11-04 12:12 ` Eli Zaretskii 2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi ` (3 more replies) 0 siblings, 4 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-04 12:12 UTC (permalink / raw) Cc: maks.romih, Angelo Graziosi, emacs-devel > Date: Mon, 30 Oct 2006 23:06:04 +0200 > From: Eli Zaretskii <eliz@gnu.org> > Cc: maks.romih@t-2.net, emacs-devel@gnu.org > > > From: Richard Stallman <rms@gnu.org> > > Date: Mon, 30 Oct 2006 14:16:28 -0500 > > Cc: emacs-devel@gnu.org > > > > > GCC-3.4.4-(1/2) Segment fault > > > > > > GCC-4.0.3 OK > > > GCC-4.1.1 OK > > > > > > GCC-4.2-20061024(prerelease) M-x undefined > > > GCC-4.3-20061022(experim.) M-x undefined > > > > > > > > > In conclusion on Cygwin only the build with GCC-4.0.3 and > 4.1.1 seem to > > > work fine. > > > > Let's document that people should not use GCC 3.4 on Cygwin. > > Where is the best place to document this? > > I will document that in etc/PROBLEMS. Done. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 22.1 Cygwin emacs timeframe query 2006-11-04 12:12 ` Eli Zaretskii @ 2006-11-21 1:28 ` Angelo Graziosi 2006-11-21 1:46 ` Angelo Graziosi ` (2 subsequent siblings) 3 siblings, 0 replies; 24+ messages in thread From: Angelo Graziosi @ 2006-11-21 1:28 UTC (permalink / raw) Cc: Eli Zaretskii Joe Buehler wrote: > I'm the maintainer for gnu emacs under Cygwin. We are happy to hear that you are still the Cygwin mantainer of Emacs! Have you recently 'frequented' the Cygwin lists ? It is almost an year that Emacs is considered an 'orphaned' package! (http://cygwin.com/ml/cygwin-apps/2005-10/msg00246.html, http://sourceware.org/ml/cygwin-apps/2006-10/msg00017.html) Cheers, Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 22.1 Cygwin emacs timeframe query 2006-11-04 12:12 ` Eli Zaretskii 2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi @ 2006-11-21 1:46 ` Angelo Graziosi 2006-11-21 9:35 ` Angelo Graziosi 2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi 3 siblings, 0 replies; 24+ messages in thread From: Angelo Graziosi @ 2006-11-21 1:46 UTC (permalink / raw) Cc: Eli Zaretskii Joe Buehler wrote: > I'm the maintainer for gnu emacs under Cygwin. Have you tried to build Emacs from CVS? What about this -------------------------------------------------------------------- .... Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name emacs Static heap usage: 10779888 of 12582912 bytes 66931 pure bytes used mv -f emacs.exe bootstrap-emacs.exe make[2]: Leaving directory `/tmp/emacs/.build/src' (cd lisp; make -w bootstrap EMACS=../src/bootstrap-emacs.exe) make[2]: Entering directory `/tmp/emacs/.build/lisp' wd=/tmp/emacs/lisp; subdirs=`(cd $wd; find . -type d -print)`; for file in $subdirs; do case $file in */Old | */RCS | */CVS | */CVS/* | */.* | */.*/* | */=* ) ;; *) wins="$wins $wd/$file" ;; esac; done; \ for file in $wins; do \ /tmp/emacs/lisp/../update-subdirs $file; \ done; wd=/tmp/emacs/lisp; subdirs=`(cd $wd; find . -type d -print)`; for file in $subdirs; do case $file in */Old | */RCS | */CVS | */CVS/* | */.* | */.*/* | */=* ) ;; *) wins="$wins $wd/$file" ;; esac; done; \ echo Directories: $wins; \ ../src/bootstrap-emacs.exe -batch --no-site-file --multibyte -l autoload --eval '(setq generated-autoload-file "/tmp/emacs/lisp/loaddefs.el")' -f batch-update-autoloads $wins Directories: /tmp/emacs/lisp/. /tmp/emacs/lisp/./calc /tmp/emacs/lisp/./calendar /tmp/emacs/lisp/./emacs-lisp /tmp/emacs/lisp/./emulation /tmp/emacs/lisp/./erc /tmp/emacs/lisp/./eshell /tmp/emacs/lisp/./gnus /tmp/emacs/lisp/./international /tmp/emacs/lisp/./language /tmp/emacs/lisp/./mail /tmp/emacs/lisp/./mh-e /tmp/emacs/lisp/./net /tmp/emacs/lisp/./obsolete /tmp/emacs/lisp/./play /tmp/emacs/lisp/./progmodes /tmp/emacs/lisp/./term /tmp/emacs/lisp/./textmodes /tmp/emacs/lisp/./url Fatal error (6)/bin/sh: line 2: 3596 Aborted (core dumped) ../src/bootstrap-emacs.exe -batch --no-site-file --multibyte -l autoload --eval '(setq generated-autoload-file "/tmp/emacs/lisp/loaddefs.el")' -f batch-update-autoloads $wins make[2]: *** [autoloads] Error 134 make[2]: Leaving directory `/tmp/emacs/.build/lisp' make[1]: *** [bootstrap-build] Error 2 make[1]: Leaving directory `/tmp/emacs/.build' make: *** [bootstrap] Error 2 -------------------------------------------------------------------- and similar failures that periodically come out in building under Cygwin? Are your build 'stable' or 'segment fault's ? The builds with gcc-4.0.3 seem very stable, those with gcc-3.4.4-1 (the only GCC in Cygwin) seem very 'unstable'. What is your results? Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 22.1 Cygwin emacs timeframe query 2006-11-04 12:12 ` Eli Zaretskii 2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi 2006-11-21 1:46 ` Angelo Graziosi @ 2006-11-21 9:35 ` Angelo Graziosi 2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi 3 siblings, 0 replies; 24+ messages in thread From: Angelo Graziosi @ 2006-11-21 9:35 UTC (permalink / raw) Cc: Eli Zaretskii Joe Buehler wrote: > I'm the maintainer for gnu emacs under Cygwin. If you are the mantainer, do you know the problems that have afflicted the Emacs-21.2-13/21.3.50-2 users in the last year? The main problem is that after a 'rebaseall' Emacs hangs. The workaround found was that after the rebase one should reinstall the non rebased version of cygncurses7.dll of the libncurses7 package. By the Cygwin mantainers it was suggested that the 'Emacs mantainer' had to rebuild Emacs linking with the new libncurses (8), at least to verify if this help. In the meanwhile, why was it not released a CVS build of Emacs (at least as exp. package, even if in Cygwin distribution there are package in 'curr' section that are taken from CVS, GDB e.g.)? Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Failures in build Emacs-CVS on Cygwin 2006-11-04 12:12 ` Eli Zaretskii ` (2 preceding siblings ...) 2006-11-21 9:35 ` Angelo Graziosi @ 2006-11-22 14:49 ` Angelo Graziosi 2006-11-22 22:23 ` Eli Zaretskii 3 siblings, 1 reply; 24+ messages in thread From: Angelo Graziosi @ 2006-11-22 14:49 UTC (permalink / raw) Cc: Eli Zaretskii Iwant to flag this for the sake of completeness. After amost a month of succeful daily build of Emacs-CVS (with GCC-4.0.3 very stable) the build fail in this way: ------------------------------------------------------------------- .... Generating autoloads for mh-utils.el... Generating autoloads for mh-utils.el...done Generating autoloads for mh-xface.el... Generating autoloads for mh-xface.el...done Saving file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/mh-e/mh-loaddefs.el... Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/mh-e/mh-loaddefs.el find /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp -name "*.elc" -print | xargs chmod +w >/dev/null 2>&1 || true; \ wd=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp; subdirs=`(cd $wd; find . -type d -print)`; for file in $subdirs; do case $file in */Old | */RCS | */CVS | */CVS/* | */.* | */.*/* | */=* ) ;; *) wins="$wins $wd/$file" ;; esac; done; \ els=`echo $wins | tr ' \011' '\012\012' | \ sed -e 's|\(.\)$|\1/|' -e 's|^\./||' -e 's|$|*.el|'`; \ for el in /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/byte-opt.el /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.el /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/progmodes/cc-mode.el /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/progmodes/cc-vars.el $els; do \ if test -f $el; \ then \ echo Compiling $el; \ EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp ../src/bootstrap-emacs.exe -batch --no-site-file --multibyte -f batch-byte-compile-if-not-done $el || exit 1; \ fi \ done Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/byte-opt.el Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/byte-opt.elc Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.el In end of data: bytecomp.el:4204:1:Warning: the function `compilation-forget-errors' is not known to be defined. Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el Fatal error (6)/bin/sh: line 4: 2196 Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp ../src/bootstrap-emacs.exe -batch --no-site-file --multibyte -f batch-byte-compile-if-not-done $el make[2]: *** [compile] Error 1 make[2]: Leaving directory `/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/lisp' make[1]: *** [bootstrap-build] Error 2 make[1]: Leaving directory `/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build' make: *** [bootstrap] Error 2 ------------------------------------------------------------------- This kind of error, periodically, comes out under Cygwin. Its structure is alway the same: Fatal error (6)/bin/sh: line <...>: <...> Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp ../src/bootstrap-emacs.exe -batch --no-site-file --multibyte -f batch-byte-compile-if-not-done $<...>. Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi @ 2006-11-22 22:23 ` Eli Zaretskii 2006-11-23 0:07 ` Angelo Graziosi 0 siblings, 1 reply; 24+ messages in thread From: Eli Zaretskii @ 2006-11-22 22:23 UTC (permalink / raw) Cc: emacs-devel > Date: Wed, 22 Nov 2006 15:49:08 +0100 (MET) > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > cc: Eli Zaretskii <eliz@gnu.org> > > Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc > Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el > Fatal error (6)/bin/sh: line 4: 2196 Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp Does Cygwin GDB support core file (a.k.a. post-mortem) debugging? If so, could you please type "gdb bootstrap-emacs.exe core" (assuming the core file's name is `core'), and see where it crashes with the "bt" command? Please run GDB from the src directory, to have it pick up all the definitions in the .gdbinit file. TIA ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-22 22:23 ` Eli Zaretskii @ 2006-11-23 0:07 ` Angelo Graziosi 2006-11-23 4:15 ` Eli Zaretskii 0 siblings, 1 reply; 24+ messages in thread From: Angelo Graziosi @ 2006-11-23 0:07 UTC (permalink / raw) Cc: Joe Buehler, emacs-devel On Thu, 23 Nov 2006, Eli Zaretskii wrote: > > Date: Wed, 22 Nov 2006 15:49:08 +0100 (MET) > > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > > cc: Eli Zaretskii <eliz@gnu.org> > > > > Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc > > Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el > > Fatal error (6)/bin/sh: line 4: 2196 Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp > > Does Cygwin GDB support core file (a.k.a. post-mortem) debugging? I think NO: there is not a 'core' file. The failure creates a file in lisp called 'bootstrap-emacs.exe.stackdump' which contains: ------------------------------------------------------------------ $ cat bootstrap-emacs.exe.stackdump Stack trace: Frame Function Args 0022A868 7C802532 (000006D0, 0000EA60, 000000A4, 0022A8B0) 0022A988 6109745C (00000000, 00000000, 00000000, 00000000) 0022AA78 61094FDB (00000000, 003B0023, 00230000, 00000000) 0022AAD8 610954BB (0022AAF0, 00000000, 00000094, 202EDC00) 0022AB98 61095672 (00000DB8, 00000006, 202DD801, 61017A53) 0022ABC8 61092AA8 (00000006, 60030000, 0022ACF8, 6109751C) 0022ACB8 61017B70 (000006D0, 0000EA60, 000000A4, 0022AD00) 0022ADD8 6109751C (00000000, 0022AED8, 20C3B800, 6101BE4E) 0022AEC8 61094FDB (00000000, 61167A20, 00000400, 61167A20) 0022AF28 610954BB (0022AF40, 00000000, 00000094, 0022AF88) 0022AFE8 61095672 (00000DB8, 00000006, 0022B018, 20151730) 0022AFF8 61092AA8 (00000000, 20CB0000, 0022B018, 20CD3000) 0022B018 20151730 (20CC0950, 211D0970, 00001AC0, 202DE004) 0022B058 201521A8 (FFFDD000, 203C0003, 0022B108, 20122139) 0022B0B8 20150951 (00004000, 202DD801, 0022B0F8, 200F28E5) 0022B0C8 200F2E3C (00004000, 203C001D, 0022D008, 0022B214) End of stack trace (more stack frames may be present) -------------------------------------------------------------- Trying your suggestion in any case, this is the result: --------------------------------------------------------- $ gdb bootstrap-emacs.exe ../lisp/bootstrap-emacs.exe.stackdump GNU gdb 6.5.50.20060706-cvs (cygwin-special) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"... "/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/src/../lisp/bootstrap-emacs.exe.stackdump" is not a core dump: File format not recognized DISPLAY = :0.0 TERM = xterm Breakpoint 1 at 0x200a0b66: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c, line 464. Breakpoint 2 at 0x200ba689: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/sysdep.c, line 1385. (gdb) bt No stack. Lisp Backtrace: Cannot access memory at address 0x22c2f8 --------------------------------------------------------- As you can see GDB says 'bootstrap-emacs.exe.stackdump is not a core dump'! Angelo. >If so, could you please type "gdb bootstrap-emacs.exe core" (assuming the > core file's name is `core'), and see where it crashes with the "bt" > command? Please run GDB from the src directory, to have it pick up > all the definitions in the .gdbinit file. > > TIA > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-23 0:07 ` Angelo Graziosi @ 2006-11-23 4:15 ` Eli Zaretskii 2006-11-23 14:04 ` Angelo Graziosi 2006-11-23 23:55 ` Angelo Graziosi 0 siblings, 2 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-23 4:15 UTC (permalink / raw) Cc: jbuehler, emacs-devel > Date: Thu, 23 Nov 2006 01:07:40 +0100 (MET) > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > cc: emacs-devel@gnu.org, Joe Buehler <jbuehler@spirentcom.com> > > On Thu, 23 Nov 2006, Eli Zaretskii wrote: > > > > Date: Wed, 22 Nov 2006 15:49:08 +0100 (MET) > > > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > > > cc: Eli Zaretskii <eliz@gnu.org> > > > > > > Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc > > > Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el > > > Fatal error (6)/bin/sh: line 4: 2196 Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp > > > > Does Cygwin GDB support core file (a.k.a. post-mortem) debugging? > > I think NO: there is not a 'core' file. The failure creates a file in lisp > called 'bootstrap-emacs.exe.stackdump' which contains: > > ------------------------------------------------------------------ > $ cat bootstrap-emacs.exe.stackdump > Stack trace: > Frame Function Args > 0022A868 7C802532 (000006D0, 0000EA60, 000000A4, 0022A8B0) > 0022A988 6109745C (00000000, 00000000, 00000000, 00000000) > 0022AA78 61094FDB (00000000, 003B0023, 00230000, 00000000) > 0022AAD8 610954BB (0022AAF0, 00000000, 00000094, 202EDC00) > 0022AB98 61095672 (00000DB8, 00000006, 202DD801, 61017A53) > 0022ABC8 61092AA8 (00000006, 60030000, 0022ACF8, 6109751C) > 0022ACB8 61017B70 (000006D0, 0000EA60, 000000A4, 0022AD00) > 0022ADD8 6109751C (00000000, 0022AED8, 20C3B800, 6101BE4E) > 0022AEC8 61094FDB (00000000, 61167A20, 00000400, 61167A20) > 0022AF28 610954BB (0022AF40, 00000000, 00000094, 0022AF88) > 0022AFE8 61095672 (00000DB8, 00000006, 0022B018, 20151730) > 0022AFF8 61092AA8 (00000000, 20CB0000, 0022B018, 20CD3000) > 0022B018 20151730 (20CC0950, 211D0970, 00001AC0, 202DE004) > 0022B058 201521A8 (FFFDD000, 203C0003, 0022B108, 20122139) > 0022B0B8 20150951 (00004000, 202DD801, 0022B0F8, 200F28E5) > 0022B0C8 200F2E3C (00004000, 203C001D, 0022D008, 0022B214) > End of stack trace (more stack frames may be present) > -------------------------------------------------------------- Please ask Cygwin experts how to produce human-readable backtrace information from this stackdump. There must be some utility in the Cygwin collection to do that. Maybe Cygwin also has a way of producing a real core file, in which case please try using it to investigate these crashes. TIA ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-23 4:15 ` Eli Zaretskii @ 2006-11-23 14:04 ` Angelo Graziosi 2006-11-23 23:55 ` Angelo Graziosi 1 sibling, 0 replies; 24+ messages in thread From: Angelo Graziosi @ 2006-11-23 14:04 UTC (permalink / raw) Cc: jbuehler, emacs-devel I have asked and Cygwin suggests this: http://cygwin.com/ml/cygwin/2006-11/msg00599.html http://cygwin.com/ml/cygwin/2006-11/msg00600.html I will try to understand deeply these suggestions to see how they work. While waiting for the above answers I downloaded new CVS (which differ very little from the previous), and now the build fails at the end of installation, i.e. after the bootstrap! --------------------------------------------------- ... ja-dic/CVS/Template ja-dic/ja-dic.el ja-dic/ja-dic.elc unset CDPATH; \ if [ -n "/usr/bin/gzip" ]; \ then \ echo "Compressing *.el ..." ; \ (cd /tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim; for f in `find . -name "*.elc" -print`; do \ /usr/bin/gzip -9n `echo $f|sed 's/.elc$/.el/'` ; \ done) \ else true; fi Compressing *.el ... chmod -R a+r /tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim make[1]: Leaving directory `/tmp/emacs/.build/leim' cd lib-src; make maybe-blessmail \ MAKE='make' archlibdir='/tmp/emacs/.inst/usr/local/emacs-cvs/libexec/emacs/22.0.91/i686-pc-cygwin' make[1]: Entering directory `/tmp/emacs/.build/lib-src' ../src/emacs -batch -l /tmp/emacs/lib-src/../lisp/mail/blessmail.el Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped) make[1]: Leaving directory `/tmp/emacs/.build/lib-src' make: *** [blessmail] Error 2 --------------------------------------------------- When all works fine, the build is completed in this way ------------------------------------------------------ ... cd lib-src; make maybe-blessmail \ MAKE='make' archlibdir='/home/Angelo/Downloads/cygwin_varie/emacs-cvs/ emacs/.inst/usr/local/emacs-cvs/libexec/emacs/22.0.90/i686-pc-cygwin' make[1]: Entering directory `/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs /.build/lib-src' ../src/emacs -batch -l /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lib-s rc/../lisp/mail/blessmail.el Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/lib-src/blessma il chmod +x blessmail Assuming /usr/spool/mail is really the mail spool directory, you should run lib-src/blessmail /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.inst/ usr/local/emacs-cvs/libexec/emacs/22.0.90/i686-pc-cygwin/movemail.exe as root, to give movemail.exe appropriate permissions. Do that after running make install. make[1]: Leaving directory `/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/ .build/lib-src' Making the binary package... =========================================== THE BUILD FINISHES AT 2006.11.18-15:12:52 =========================================== ------------------------------------------------------ Cheers, Angelo. On Thu, 23 Nov 2006, Eli Zaretskii wrote: > > Date: Thu, 23 Nov 2006 01:07:40 +0100 (MET) > > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > > cc: emacs-devel@gnu.org, Joe Buehler <jbuehler@spirentcom.com> > > > > On Thu, 23 Nov 2006, Eli Zaretskii wrote: > > > > > > Date: Wed, 22 Nov 2006 15:49:08 +0100 (MET) > > > > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > > > > cc: Eli Zaretskii <eliz@gnu.org> > > > > > > > > Wrote /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc > > > > Compiling /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el > > > > Fatal error (6)/bin/sh: line 4: 2196 Aborted (core dumped) EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp > > > > > > Does Cygwin GDB support core file (a.k.a. post-mortem) debugging? > > > > I think NO: there is not a 'core' file. The failure creates a file in lisp > > called 'bootstrap-emacs.exe.stackdump' which contains: > > > > ------------------------------------------------------------------ > > $ cat bootstrap-emacs.exe.stackdump > > Stack trace: > > Frame Function Args > > 0022A868 7C802532 (000006D0, 0000EA60, 000000A4, 0022A8B0) > > 0022A988 6109745C (00000000, 00000000, 00000000, 00000000) > > 0022AA78 61094FDB (00000000, 003B0023, 00230000, 00000000) > > 0022AAD8 610954BB (0022AAF0, 00000000, 00000094, 202EDC00) > > 0022AB98 61095672 (00000DB8, 00000006, 202DD801, 61017A53) > > 0022ABC8 61092AA8 (00000006, 60030000, 0022ACF8, 6109751C) > > 0022ACB8 61017B70 (000006D0, 0000EA60, 000000A4, 0022AD00) > > 0022ADD8 6109751C (00000000, 0022AED8, 20C3B800, 6101BE4E) > > 0022AEC8 61094FDB (00000000, 61167A20, 00000400, 61167A20) > > 0022AF28 610954BB (0022AF40, 00000000, 00000094, 0022AF88) > > 0022AFE8 61095672 (00000DB8, 00000006, 0022B018, 20151730) > > 0022AFF8 61092AA8 (00000000, 20CB0000, 0022B018, 20CD3000) > > 0022B018 20151730 (20CC0950, 211D0970, 00001AC0, 202DE004) > > 0022B058 201521A8 (FFFDD000, 203C0003, 0022B108, 20122139) > > 0022B0B8 20150951 (00004000, 202DD801, 0022B0F8, 200F28E5) > > 0022B0C8 200F2E3C (00004000, 203C001D, 0022D008, 0022B214) > > End of stack trace (more stack frames may be present) > > -------------------------------------------------------------- > > Please ask Cygwin experts how to produce human-readable backtrace > information from this stackdump. There must be some utility in the > Cygwin collection to do that. > > Maybe Cygwin also has a way of producing a real core file, in which > case please try using it to investigate these crashes. > > TIA > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-23 4:15 ` Eli Zaretskii 2006-11-23 14:04 ` Angelo Graziosi @ 2006-11-23 23:55 ` Angelo Graziosi 2006-11-24 21:17 ` Eli Zaretskii 1 sibling, 1 reply; 24+ messages in thread From: Angelo Graziosi @ 2006-11-23 23:55 UTC (permalink / raw) Cc: jbuehler, emacs-devel On Thu, 23 Nov 2006, Eli Zaretskii wrote: > Maybe Cygwin also has a way of producing a real core file, in which > case please try using it to investigate these crashes. > Configuring the CYGWIN env. variable, when bootstrapping, it creates lisp/bootstrap-emacs.exe.core, so I have tried the following (I am not a very expert of GDB) Using 'run' under GDB, it hangs and I must kill it: --------------------------------------------------------------- $ gdb ./bootstrap-emacs.exe ../lisp/bootstrap-emacs.exe.core GNU gdb 6.5.50.20060706-cvs (cygwin-special) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"... warning: core file may not match specified executable file. warning: Couldn't find general-purpose registers in core file. warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? () DISPLAY = :0.0 TERM = xterm Breakpoint 1 at 0x200a0b66: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c, line 464. Breakpoint 2 at 0x200ba689: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/sysdep.c, line 1385. (gdb) run Starting program: /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/src/bootstrap-emacs.exe -geometry 80x40+0+0 Loaded symbols for /c/WINDOWS/system32/ntdll.dll Loaded symbols for /c/WINDOWS/system32/kernel32.dll Loaded symbols for /usr/X11R6/bin/cygICE-6.dll Loaded symbols for /usr/bin/cygwin1.dll Loaded symbols for /c/WINDOWS/system32/advapi32.dll Loaded symbols for /c/WINDOWS/system32/rpcrt4.dll Loaded symbols for /usr/X11R6/bin/cygSM-6.dll Loaded symbols for /usr/X11R6/bin/cygX11-6.dll Loaded symbols for /usr/X11R6/bin/cygXaw3d-7.dll Loaded symbols for /usr/X11R6/bin/cygXext-6.dll Loaded symbols for /usr/X11R6/bin/cygXmu-6.dll Loaded symbols for /usr/X11R6/bin/cygXt-6.dll Loaded symbols for /usr/X11R6/bin/cygXpm-4.dll Loaded symbols for /usr/bin/cygncurses-8.dll Loaded symbols for /usr/bin/cygjpeg-62.dll Loaded symbols for /usr/bin/cygpng12.dll Loaded symbols for /usr/bin/cygz.dll Loaded symbols for /usr/bin/cygtiff-5.dll Loaded symbols for /usr/bin/cygungif-4.dll warning: NOD32 protected [MSAFD Tcpip [TCP/IP]] warning: NOD32 protected [MSAFD Tcpip [UDP/IP]] warning: NOD32 protected [MSAFD Tcpip [RAW/IP]] warning: NOD32 protected [RSVP UDP Service Provider] warning: NOD32 protected [RSVP TCP Service Provider] ***** HERE IT HANGS ! ****** Program received signal SIGSEGV, Segmentation fault. ---Type <return> to continue, or q <return> to quit---[2]+ Killed gdb ./bootstrap-emacs.exe ../lisp/bootstrap-emacs.exe.core Killed --------------------------------------------------------------- Using 'start', 'bt' and 'c' in GDB (after 'c' it hangs as above): ---------------------------------------------------------- $ gdb ./bootstrap-emacs.exe ../lisp/bootstrap-emacs.exe.core GNU gdb 6.5.50.20060706-cvs (cygwin-special) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"... warning: core file may not match specified executable file. warning: Couldn't find general-purpose registers in core file. warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? () DISPLAY = :0.0 TERM = xterm Breakpoint 1 at 0x200a0b66: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c, line 464. Breakpoint 2 at 0x200ba689: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/sysdep.c, line 1385. (gdb) start Breakpoint 3 at 0x200a1a4e: file /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c, line 837. Starting program: /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/src/bootstrap-emacs.exe -geometry 80x40+0+0 Loaded symbols for /c/WINDOWS/system32/ntdll.dll Loaded symbols for /c/WINDOWS/system32/kernel32.dll Loaded symbols for /usr/X11R6/bin/cygICE-6.dll Loaded symbols for /usr/bin/cygwin1.dll Loaded symbols for /c/WINDOWS/system32/advapi32.dll Loaded symbols for /c/WINDOWS/system32/rpcrt4.dll Loaded symbols for /usr/X11R6/bin/cygSM-6.dll Loaded symbols for /usr/X11R6/bin/cygX11-6.dll Loaded symbols for /usr/X11R6/bin/cygXaw3d-7.dll Loaded symbols for /usr/X11R6/bin/cygXext-6.dll Loaded symbols for /usr/X11R6/bin/cygXmu-6.dll Loaded symbols for /usr/X11R6/bin/cygXt-6.dll Loaded symbols for /usr/X11R6/bin/cygXpm-4.dll Loaded symbols for /usr/bin/cygncurses-8.dll Loaded symbols for /usr/bin/cygjpeg-62.dll Loaded symbols for /usr/bin/cygpng12.dll Loaded symbols for /usr/bin/cygz.dll Loaded symbols for /usr/bin/cygtiff-5.dll Loaded symbols for /usr/bin/cygungif-4.dll main (argc=3, argv=0x202d3040) at /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c:837 837 { (gdb) bt #0 main (argc=3, argv=0x202d3040) at /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c:837 Lisp Backtrace: 0 (0x909090c3) Cannot access memory at address 0x78746344 (gdb) q The program is running. Exit anyway? (y or n) n Not confirmed. (gdb) c Continuing. warning: NOD32 protected [MSAFD Tcpip [TCP/IP]] warning: NOD32 protected [MSAFD Tcpip [UDP/IP]] warning: NOD32 protected [MSAFD Tcpip [RAW/IP]] warning: NOD32 protected [RSVP UDP Service Provider] warning: NOD32 protected [RSVP TCP Service Provider] Program received signal SIGSEGV, Segmentation fault. [Switching to thread 3136.0xc94] 0x00000000 in ?? () (gdb) Killed ---------------------------------------------------------- The results do not look very encouraging! Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-23 23:55 ` Angelo Graziosi @ 2006-11-24 21:17 ` Eli Zaretskii 2006-11-24 23:32 ` Angelo Graziosi 2006-11-25 9:52 ` Angelo Graziosi 0 siblings, 2 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-24 21:17 UTC (permalink / raw) Cc: jbuehler, emacs-devel > Date: Fri, 24 Nov 2006 00:55:10 +0100 (MET) > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > cc: emacs-devel@gnu.org, jbuehler@spirentcom.com > > Configuring the CYGWIN env. variable, when bootstrapping, it creates > lisp/bootstrap-emacs.exe.core, so I have tried the following (I am not a > very expert of GDB) > > Using 'run' under GDB, it hangs and I must kill it: > --------------------------------------------------------------- > $ gdb ./bootstrap-emacs.exe ../lisp/bootstrap-emacs.exe.core > GNU gdb 6.5.50.20060706-cvs (cygwin-special) > Copyright (C) 2006 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i686-pc-cygwin"... > > warning: core file may not match specified executable file. > > warning: Couldn't find general-purpose registers in core file. > > warning: Couldn't find general-purpose registers in core file. These 3 messages aren't a good sign. > #0 0x00000000 in ?? () > DISPLAY = :0.0 > TERM = xterm > Breakpoint 1 at 0x200a0b66: file > /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/emacs.c, line 464. > Breakpoint 2 at 0x200ba689: file > /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/src/sysdep.c, line > 1385. > (gdb) run No, you shouldn't run the program. You are debugging a core file, which is an image of a dead program. Such a program cannot be run. You can only examine the variables and memory. So the right command is "bt". ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-24 21:17 ` Eli Zaretskii @ 2006-11-24 23:32 ` Angelo Graziosi 2006-11-25 11:07 ` Eli Zaretskii 2006-11-25 9:52 ` Angelo Graziosi 1 sibling, 1 reply; 24+ messages in thread From: Angelo Graziosi @ 2006-11-24 23:32 UTC (permalink / raw) Cc: emacs-devel On Fri, 24 Nov 2006, Eli Zaretskii wrote: > > (gdb) run > > No, you shouldn't run the program. You are debugging a core file, > which is an image of a dead program. Such a program cannot be run. > You can only examine the variables and memory. So the right command > is "bt". > I tried it, first, but I obtained only a "Cannot access memory at address...", so I tried the others. Meanwhile I have continued to build new CVS and now the build is completed successfully! The mystery is that also with previous CVS the problems cannot be reproduced any more! This is what happens on Cygwin! On GNU/Linux I have not found obstacles in build Emacs-CVS. Thanks for your recent post on Cygwin lists. Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-24 23:32 ` Angelo Graziosi @ 2006-11-25 11:07 ` Eli Zaretskii 0 siblings, 0 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-25 11:07 UTC (permalink / raw) Cc: emacs-devel > Date: Sat, 25 Nov 2006 00:32:42 +0100 (MET) > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > cc: emacs-devel@gnu.org > > Thanks for your recent post on Cygwin lists. I just couldn't stand anymore the kind of unfriendly replies that are evidently a norm on that list. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-24 21:17 ` Eli Zaretskii 2006-11-24 23:32 ` Angelo Graziosi @ 2006-11-25 9:52 ` Angelo Graziosi 2006-11-25 11:06 ` Eli Zaretskii 1 sibling, 1 reply; 24+ messages in thread From: Angelo Graziosi @ 2006-11-25 9:52 UTC (permalink / raw) Cc: jbuehler, emacs-devel I post this only for the sake of completeness. When the build fails as described here: http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg01214.html, having activated the dumper.exe so that a core file is produced the results are the following. At the end of installation the build fails in this way: ----------------------------------------------------------- ... ja-dic/CVS/Template ja-dic/ja-dic.el ja-dic/ja-dic.elc unset CDPATH; \ if [ -n "/usr/bin/gzip" ]; \ then \ echo "Compressing *.el ..." ; \ (cd /tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim; fo r f in `find . -name "*.elc" -print`; do \ /usr/bin/gzip -9n `echo $f|sed 's/.elc$/.el/'` ; \ done) \ else true; fi Compressing *.el ... chmod -R a+r /tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim make[1]: Leaving directory `/tmp/emacs/.build/leim' cd lib-src; make maybe-blessmail \ MAKE='make' archlibdir='/tmp/emacs/.inst/usr/local/emacs-cvs/libexec/e macs/22.0.91/i686-pc-cygwin' make[1]: Entering directory `/tmp/emacs/.build/lib-src' ../src/emacs -batch -l /tmp/emacs/lib-src/../lisp/mail/blessmail.el Fatal error (6)*** starting debugger for pid 740, tid 2388 *** continuing pid 740 from debugger call (1) make[1]: *** [blessmail] Aborted (core dumped) make[1]: Leaving directory `/tmp/emacs/.build/lib-src' make: *** [blessmail] Error 2 ----------------------------------------------------------- this creates a emacs.exe.core file of about 20MB. Using GDB: ------------------------------------------------------------ /tmp/emacs/.build/src $ gdb ./emacs.exe ../lib-src/emacs.exe.core GNU gdb 6.5.50.20060706-cvs (cygwin-special) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"... warning: core file may not match specified executable file. warning: Couldn't find general-purpose registers in core file. warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? () Environment variable "DISPLAY" not defined. TERM = cygwin Breakpoint 1 at 0x200a0b66: file /tmp/emacs/src/emacs.c, line 464. Breakpoint 2 at 0x200ba689: file /tmp/emacs/src/sysdep.c, line 1385. (gdb) bt #0 0x00000000 in ?? () Lisp Backtrace: Cannot access memory at address 0x22c2f8 (gdb) ------------------------------------------------------------ Using the suggestion http://cygwin.com/ml/cygwin/2006-11/msg00657.html ------------------------------------------------------------------------ /tmp/emacs/.build/lib-src $ awk '/^[0-9]/{print $2}' emacs.exe.stackdump | addr2line -f -e ../src/emacs.exe > /tmp/out /tmp cat out ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 ?? ??:0 relinquish /tmp/emacs/src/ralloc.c:338 r_alloc_sbrk /tmp/emacs/src/ralloc.c:934 _malloc_internal /tmp/emacs/src/gmalloc.c:504 emacs_blocked_malloc /tmp/emacs/src/alloc.c:1244 ------------------------------------------------------------------------ Cheers, Angelo. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Failures in build Emacs-CVS on Cygwin 2006-11-25 9:52 ` Angelo Graziosi @ 2006-11-25 11:06 ` Eli Zaretskii 0 siblings, 0 replies; 24+ messages in thread From: Eli Zaretskii @ 2006-11-25 11:06 UTC (permalink / raw) Cc: jbuehler, emacs-devel > Date: Sat, 25 Nov 2006 10:52:42 +0100 (MET) > From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> > cc: emacs-devel@gnu.org, jbuehler@spirentcom.com > > relinquish > /tmp/emacs/src/ralloc.c:338 > r_alloc_sbrk > /tmp/emacs/src/ralloc.c:934 > _malloc_internal > /tmp/emacs/src/gmalloc.c:504 > emacs_blocked_malloc > /tmp/emacs/src/alloc.c:1244 Looks like some problem with memory allocation. Several similar crashes of the Cygwin port were reported during the last months, IIRC. ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2006-11-25 11:07 UTC | newest] Thread overview: 24+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-10-30 1:22 Building Emacs-cvs on Cygwin (GCC summary) Maks Romih 2006-10-30 19:16 ` Richard Stallman 2006-10-30 20:31 ` Eric Hanchrow 2006-10-30 21:05 ` Eli Zaretskii 2006-10-30 21:26 ` Eric Hanchrow 2006-10-30 21:44 ` Jason Rumney 2006-11-05 10:52 ` Jari Aalto 2006-11-05 11:55 ` Eli Zaretskii 2006-10-30 21:06 ` Eli Zaretskii 2006-11-04 12:12 ` Eli Zaretskii 2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi 2006-11-21 1:46 ` Angelo Graziosi 2006-11-21 9:35 ` Angelo Graziosi 2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi 2006-11-22 22:23 ` Eli Zaretskii 2006-11-23 0:07 ` Angelo Graziosi 2006-11-23 4:15 ` Eli Zaretskii 2006-11-23 14:04 ` Angelo Graziosi 2006-11-23 23:55 ` Angelo Graziosi 2006-11-24 21:17 ` Eli Zaretskii 2006-11-24 23:32 ` Angelo Graziosi 2006-11-25 11:07 ` Eli Zaretskii 2006-11-25 9:52 ` Angelo Graziosi 2006-11-25 11:06 ` Eli Zaretskii
Code repositories for project(s) associated with this external index https://git.savannah.gnu.org/cgit/emacs.git https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.