From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, angelo.graziosi@alice.it
Subject: Re: The bootstrap of Emacs on Cygwin is broken [Is also: unicode branch is merged to trunk]
Date: Mon, 04 Feb 2008 08:58:54 +0000 [thread overview]
Message-ID: <47A6D3CE.5000405@gnu.org> (raw)
In-Reply-To: <u1w7tuzij.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Sun, 03 Feb 2008 21:02:55 +0000
>> From: Jason Rumney <jasonr@gnu.org>
>> CC: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>>
>> Angelo Graziosi wrote:
>>
>>> (gdb) bt
>>> #0 0x610e1805 in _vfprintf_r () from /usr/bin/cygwin1.dll
>>> #1 0x610f0358 in printf () from /usr/bin/cygwin1.dll
>>> #2 0x610933b8 in _sigfe () from /usr/bin/cygwin1.dll
>>> #3 0x00bfba30 in ?? ()
>>> #4 0x00020000 in ?? ()
>>> #5 0x20ef0000 in bss_sbrk_buffer ()
>>> #6 0x00020000 in ?? ()
>>> #7 0x00033668 in ?? ()
>>> ...
>>> #14 0x61057dbc in malloc () from /usr/bin/cygwin1.dll
>>> #15 0x00010000 in ?? ()
>>> #16 0x00000000 in ?? ()
>>> (gdb)
>>>
>> There are no Emacs symbols in there.
>>
>
> The portions you omitted (frames 8 to 13) did include Emacs symbols,
> such as `obtain' and `r_alloc_sbrk'.
>
I didn't recognize those. I was expecting to see main and
Frecursive_edit in the last two places.
next prev parent reply other threads:[~2008-02-04 8:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 20:32 The bootstrap of Emacs on Cygwin is broken [Is also: unicode branch is merged to trunk] Angelo Graziosi
2008-02-02 18:03 ` Eli Zaretskii
2008-02-02 19:32 ` Angelo Graziosi
2008-02-02 19:43 ` Eli Zaretskii
2008-02-02 21:21 ` Angelo Graziosi
2008-02-03 4:10 ` Eli Zaretskii
2008-02-03 9:19 ` Angelo Graziosi
2008-02-03 19:40 ` Eli Zaretskii
2008-02-03 21:02 ` Angelo Graziosi
2008-02-03 21:02 ` Jason Rumney
2008-02-03 21:14 ` Angelo Graziosi
2008-02-04 4:19 ` Eli Zaretskii
2008-02-04 8:39 ` Angelo Graziosi
2008-02-04 9:00 ` YAMAMOTO Mitsuharu
2008-02-04 10:35 ` Angelo Graziosi
2008-02-04 11:01 ` YAMAMOTO Mitsuharu
2008-02-04 11:11 ` Jason Rumney
2008-02-04 20:55 ` Eli Zaretskii
2008-02-04 22:07 ` Angelo Graziosi
2008-02-05 4:17 ` Eli Zaretskii
2008-02-05 2:10 ` Angelo Graziosi
2008-02-05 4:17 ` Eli Zaretskii
2008-02-05 10:12 ` Angelo Graziosi
2008-02-05 10:19 ` Jason Rumney
2008-02-05 10:52 ` Angelo Graziosi
2008-02-05 11:10 ` Jason Rumney
2008-02-05 12:03 ` Angelo Graziosi
2008-02-05 20:17 ` Eli Zaretskii
2008-02-05 20:49 ` Angelo Graziosi
2008-02-06 4:10 ` Eli Zaretskii
2008-02-06 15:27 ` Angelo Graziosi
2008-05-28 2:15 ` Jashy
2008-05-28 3:06 ` Stefan Monnier
2008-05-28 3:21 ` YAMAMOTO Mitsuharu
2008-02-05 17:22 ` Angelo Graziosi
2008-02-04 4:16 ` Eli Zaretskii
2008-02-04 8:58 ` Jason Rumney [this message]
2008-02-02 18:03 ` Dan Nicolaescu
2008-02-02 18:32 ` Eli Zaretskii
2008-05-28 7:42 ` Angelo Graziosi
2008-05-28 10:20 ` Jashy
2008-05-28 10:30 ` YAMAMOTO Mitsuharu
2008-05-28 11:36 ` Jashy
2008-05-28 12:06 ` YAMAMOTO Mitsuharu
2008-05-28 13:16 ` Jashy
2008-05-28 17:21 ` Angelo Graziosi
2008-05-29 0:38 ` YAMAMOTO Mitsuharu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A6D3CE.5000405@gnu.org \
--to=jasonr@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).