From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>
Cc: emacs-devel@gnu.org
Subject: Re: Failures in build Emacs-CVS on Cygwin
Date: Sat, 25 Nov 2006 00:32:42 +0100 (MET) [thread overview]
Message-ID: <Pine.OSF.4.21.0611250020280.13913-100000@ax0rm1.roma1.infn.it> (raw)
In-Reply-To: <u3b887dds.fsf@gnu.org>
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.
next prev parent reply other threads:[~2006-11-24 23:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-11-25 11:07 ` Eli Zaretskii
2006-11-25 9:52 ` Angelo Graziosi
2006-11-25 11:06 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.OSF.4.21.0611250020280.13913-100000@ax0rm1.roma1.infn.it \
--to=angelo.graziosi@roma1.infn.it \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.