unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Charles A. Roelli" <charles@aurox.ch>
To: Alan Third <alan@idiocy.org>
Cc: Keith David Bershatsky <esq@lawlist.com>,
	27736@debbugs.gnu.org,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#27736: OSX 10.6.8: Building from master branch fails.
Date: Sun, 23 Jul 2017 11:28:54 +0200	[thread overview]
Message-ID: <04c8d036-d234-5d8c-22a4-b505224255f7@aurox.ch> (raw)
In-Reply-To: <20170719224801.GA57066@breton.holly.idiocy.org>

I have no idea why the code goes into an infinite loop, but it seems
somebody else has already had the same problem (on FreeBSD, the source
of Apple's libc):

https://rt.cpan.org/Public/Bug/Display.html?id=40764

They have a freeze on the same value of "time" that we have:

(gdb) frame 4
#4  0x00000001002b9d8b in emacs_localtime_rz (tz=0x102102a60, 
t=0x7fff5fbe8b80, tm=0x7fff5fbe8b48) at editfns.c:103
103      tm = localtime_rz (tz, t, tm);
(gdb) ptype t
type = long *
(gdb) p *t
$2 = -67768038400720896

Somebody in the linked thread also had the same problem on macOS. And
apparently NetBSD had some of the same issues (search for "infinite
loop in localtime" on the linked page):

http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/time/localtime.c?only_with_tag=MAIN

But I'm not sure those fixes would have anything to do with macOS.


On 20/07/2017 00:48, Alan Third wrote:
> On Wed, Jul 19, 2017 at 09:58:03PM +0200, Charles A. Roelli wrote:
>> Err, oops: I guess there will be no patch for this in Lisp, since
>> decode-time is written in C.
>>
>>
>> So the choice is either to make a change in lib/time_rz.c or src/editfns.c.
> Do you know what the actual problem is? If it’s going into an infinite
> loop, why is that happening? That might give us a better idea where
> the fix should go.
>






  reply	other threads:[~2017-07-23  9:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 15:18 bug#27736: OSX 10.6.8: Building from master branch fails Keith David Bershatsky
2017-07-17 15:29 ` Noam Postavsky
2017-07-17 16:10 ` Keith David Bershatsky
2017-07-17 16:38   ` Noam Postavsky
2017-07-17 18:05 ` Keith David Bershatsky
2017-07-17 18:48   ` Noam Postavsky
2017-07-17 19:43 ` Alan Third
2017-07-17 20:48   ` Charles A. Roelli
2017-07-17 21:37 ` Keith David Bershatsky
2017-07-18  5:08   ` Charles A. Roelli
2017-07-18  6:56 ` Keith David Bershatsky
2017-07-18 14:34   ` Eli Zaretskii
2017-07-18 16:07 ` Keith David Bershatsky
2017-07-18 18:42   ` Charles A. Roelli
2017-07-19 19:58     ` Charles A. Roelli
2017-07-19 22:48       ` Alan Third
2017-07-23  9:28         ` Charles A. Roelli [this message]
2017-07-24 15:50           ` Glenn Morris
2017-07-30 16:32             ` Charles A. Roelli
2017-11-05 18:03 ` Keith David Bershatsky
2017-11-05 18:15   ` Noam Postavsky
2017-11-05 20:01 ` Keith David Bershatsky
2017-11-06  2:20 ` Keith David Bershatsky
2017-11-06 19:41   ` Charles A. Roelli
2017-11-06 20:41     ` Charles A. Roelli
2017-11-07  2:13 ` Keith David Bershatsky
2017-11-07 20:20   ` Charles A. Roelli
2017-11-08  5:18 ` Keith David Bershatsky
2017-11-08 19:55   ` Charles A. Roelli
2018-03-27 21:19 ` Paul Eggert
2018-03-28 17:15   ` Glenn Morris
2018-03-28 19:02     ` Charles A. Roelli
2018-03-28 19:33     ` Paul Eggert
2018-03-28 22:08       ` Paul Eggert
2018-03-28 18:54   ` Charles A. Roelli
2018-03-28 21:29     ` Paul Eggert
     [not found]     ` <805d95e1-bfc0-bb40-ced7-c10bb5a7256e@cs.ucla.edu>
2018-03-31 15:02       ` Charles A. Roelli
     [not found]       ` <m21sg02sr4.fsf@aurox.ch>
2018-04-01 20:32         ` Paul Eggert
     [not found] <m2a800ve9b.wl%esq@lawlist.com>
2017-11-05 20:54 ` Charles A. Roelli

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=04c8d036-d234-5d8c-22a4-b505224255f7@aurox.ch \
    --to=charles@aurox.ch \
    --cc=27736@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=esq@lawlist.com \
    --cc=npostavs@users.sourceforge.net \
    /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).