public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: rebase segmentation fault
Date: Sun, 16 Jul 2017 19:39:00 -0000	[thread overview]
Message-ID: <8c4637af-09b1-18dc-2ff8-7dabfbc6824b@cs.umass.edu> (raw)
In-Reply-To: <EC918951-4A16-4469-B057-5DEC00041699@Denis-Excoffier.org>

On 7/16/2017 1:16 PM, 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.
>
> I must confess that my system contains all the available packages (except for debuginfo ones), and the rebase_all contains 9275 lines.
> Later, i uninstalled a few packages (a few categories in fact), and my rebase_all contained 8337 lines, rebase worked well and
> /etc/rebase.db.i386 was present.
>
> Question: how is 'rebase' supposed to notify the user that the list of files is too large (i.e. that the overall amount of DLL sizes
> is more than 0x070000000)? In source code, i found no specific message to indicate this.

I would find notification of such overflow useful as well.

And once I have over-committed by installing too many packages,
I have found it rather difficult to figure out what to remove
that will actually help, given the general snarl of dependencies
of one thing on another ...  Maybe there is room for another tool
that works over the database and helps determine what can be done.

Regards - Eliot Moss

--
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

  reply	other threads:[~2017-07-16 17:39 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 [this message]
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
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=8c4637af-09b1-18dc-2ff8-7dabfbc6824b@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).