all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: latest-from-bzr segfaults easily
Date: Fri, 27 May 2011 11:17:01 +0200	[thread overview]
Message-ID: <87tycgzenm.fsf@rho.meyering.net> (raw)
In-Reply-To: <87sjs2aa6t.fsf@rho.meyering.net> (Jim Meyering's message of "Wed, 25 May 2011 20:48:10 +0200")

Jim Meyering wrote:

> Paul Eggert wrote:
>
>> On 05/25/11 04:41, Jim Meyering wrote:
>>> The latest is not usable for me on Fedora 15, x86_64.
>>>
>>> How to reproduce using emacs built from the latest bzr
>>> sources of about 5 hours ago:
>>>
>>> First, get a cloned copy of the dash sources:
>>> (you can probably use C source file, but this is particularly reliable)
>>>
>>>    git clone git://git.kernel.org/pub/scm/utils/dash/dash.git && cd dash
>>>
>>> Then, run this and type `C-s sh_':
>>>
>>>   $ /p/p/emacs-2011-05-25.08h03/bin/emacs -q src/error.c
>>>   Fatal error (11)zsh: abort (core dumped)
>>
>> I can't reproduce the problem on Fedora 14, x86_64.
>> I used bzr 104366 and the command:
>>
>>   ~/src/gnu/emacs/trunkclone/src/emacs -q src/error.c
>>
>> It could be a Fedora 15 thing, or it could be something else
>> different in our setups.
>>
>> I recall having a similer problem on Ubuntu 10.10 that I tracked
>> down to a bug in the glibc string headers: they had marked memmove's
>> parameters to be 'restrict', which is quite bogus, and caused
>> GCC 4.6.0 to generate incorrect code.  Are you using GCC 4.6.0?
>
> Yes, but the head from just a dozen hours earlier works fine.
> I'll end up using bisection, if I find the time.

Luckily(?) the problem disappeared when I rebuilt
with the latest from some time yesterday.



      reply	other threads:[~2011-05-27  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 11:41 latest-from-bzr segfaults easily Jim Meyering
2011-05-25 16:23 ` Eli Zaretskii
2011-05-25 17:18 ` Paul Eggert
2011-05-25 18:48   ` Jim Meyering
2011-05-27  9:17     ` Jim Meyering [this message]

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=87tycgzenm.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=eggert@cs.ucla.edu \
    --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.