From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: core dump on rebaseall [attn ocaml maintainer]
Date: Fri, 26 Feb 2016 23:31:00 -0000 [thread overview]
Message-ID: <56D0E052.4050501@gmail.com> (raw)
In-Reply-To: <CAOWw6Hdkp63bhgD8Gm1PyQ3sbc9YU6tLbz+FVMEh_2c+emG=aQ@mail.gmail.com>
On 27/02/2016 00:06, Michael Steiner wrote:
> On 02/24/2016 08:15 PM, "Larry Hall (Cygwin)" wrote:
>
>
>
> However, above triggered a though: i've previously looked into
> rebaseall and tried to briefly isolate the problem by pruning
> rebase.lst which created to be fed to rebase. Unfortunately, just
> removing lines from the back caused for a while still the core dump
> and then eventually complained that some files could not be fixed.
> Looking at it again it seems the files which are causing the trouble
> are following ocaml files!
>
> < /usr/lib/ocaml/stublibs/dllbigarray.so
> < /usr/lib/ocaml/stublibs/dllcamlstr.so
> < /usr/lib/ocaml/stublibs/dllgraphics.so
> < /usr/lib/ocaml/stublibs/dllnums.so
> < /usr/lib/ocaml/stublibs/dllthreads.so
> < /usr/lib/ocaml/stublibs/dllunix.so
> < /usr/lib/ocaml/stublibs/dllvmthreads.so
>
> with them included, running
>
> rebase -n -s -8 -b 0x400000000 -o 0 -T /tmp/rebase.lst
>
> coredumps. if i exclude them, then it works!
It seems only one file with that defect:
$ rebase -b 0x400000000 /usr/lib/ocaml/stublibs/dllunix.so
Segmentation fault (core dumped)
$ rebase -i /usr/lib/ocaml/stublibs/dllunix.so
Segmentation fault (core dumped)
--
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
prev parent reply other threads:[~2016-02-26 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 23:30 core dump on rebaseall Michael Steiner
2016-02-25 1:15 ` Larry Hall (Cygwin)
2016-02-26 23:06 ` Michael Steiner
2016-02-26 23:31 ` Marco Atzeri [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=56D0E052.4050501@gmail.com \
--to=marco.atzeri@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).