From: Erik Bray <erik.m.bray@gmail.com>
To: cygwin@cygwin.com
Subject: Re: rebase segmentation fault
Date: Tue, 18 Jul 2017 16:30:00 -0000 [thread overview]
Message-ID: <CAOTD34bWPjLbKUJjiyCY23G9ZbjfCkyNepqd3g+0xKc49A+OFw@mail.gmail.com> (raw)
In-Reply-To: <20170717090522.GB3345@calimero.vinschen.de>
On Mon, Jul 17, 2017 at 11:05 AM, Corinna Vinschen wrote:
> On Jul 17 10:35, Corinna Vinschen wrote:
>> On Jul 16 19:16, Denis Excoffier wrote:
>> > Hello,
>> >
>> > I have a Cygwin installation under Windows 7 (32 bits).
>> >
>> > After 'rebase-trigger full' and 'Setup', autorebase seems to finish
>> > okay, but the /etc/rebase.db.i386 remains absent after that. Not a
>> > real problem after all (since rebase was functioning well until some
>> > recent date and all is already rebased), but some third party builds
>> > (like e.g. perl) insist on the presence of the /etc/rebase.db.i386
>> > database.
>> >
>> > Indeed, rebase segfaults in rebase.c and nothing is rebased. This
>> > occurs (see rebase-4.4.2) immediately after "Skip trailing entries as
>> > long as there is no hole." because at some point, all
>> > img_info_list[end].base are equal to 0, the while() is getting always
>> > true, and the variable 'end' is decremented by 1 at every iteration,
>> > until it reaches -1 where the segfault occurs.
>>
>> Patches welcome!
>
> Never mind:
>
> https://sourceware.org/git/?p=cygwin-apps/rebase.git;a=commitdiff;h=a7d415a
Thanks! I've been bitten by this in the past as well, but wasn't
sufficiently motivated to chase down the fix once I knew what the
problem was :)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-18 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 17:22 Denis Excoffier
2017-07-16 19:39 ` Eliot Moss
2017-07-16 23:33 ` David Stacey
2017-07-17 9:05 ` Corinna Vinschen
2017-07-17 11:35 ` Corinna Vinschen
2017-07-18 16:30 ` Erik Bray [this message]
2018-01-09 17:53 ` Denis Excoffier
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=CAOTD34bWPjLbKUJjiyCY23G9ZbjfCkyNepqd3g+0xKc49A+OFw@mail.gmail.com \
--to=erik.m.bray@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).