From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: core dump on rebaseall
Date: Thu, 25 Feb 2016 01:15:00 -0000 [thread overview]
Message-ID: <56CE55AD.4060304@cygwin.com> (raw)
In-Reply-To: <CAOWw6HeauyU5+XpTzrXziB8DXtg0P2Y0Wb_+mKeU9NHkWNZdPA@mail.gmail.com>
On 02/24/2016 06:30 PM, Michael Steiner wrote:
> Hi,
>
> Chasing a vfork issue in emacs prevening on sub-shell or dired on a
> uptodate cygwin install, i followed the FAQ and tried to do a
> rebaseall. Unfortunately, that resulted in a core dump with the
> rebase.exe.statckdump mentioning a STATUS_ACCESS_VIOLATION problem! I
> then also noticed, that an update with the latest version of the
> setup.exe also causes a rebase.exe.stackdump in c:\cygwin64!.
> Subsequent attempts rebasing in safe mode or after re-installing
> everything (via setup and click on All until it says re-install) had
> the same problem, as did upgrading cyginw, cygwin-debuginfo and
> cygwin-devel from the current 2.4.1-1 to 2.5.0.4 :-( [The vfork
> problem in emacs, though, did disappear ..]
>
> I have cygwin running via a few months and didn't change anything in
> the config recently (although i did run setup to update to latest
> version). Unfortunately, i have no idea when setup also caused to
> coredump on rebase. It might have done it already for a while but as
> it doesn't complain, i have no idea when the rebase.exe.stackdump
> started showing up in c:\cygwin64.
>
> I googled for this problem but couldn't find any references to rebase
> itself failing. Anybody has an idea what's going on and/or how to
> debug or work around?
Did you stop your services before upgrading/rebasing? Do you have
any Cygwin executables or DLLs that aren't part of the distribution?
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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:[~2016-02-25 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 23:30 Michael Steiner
2016-02-25 1:15 ` Larry Hall (Cygwin) [this message]
2016-02-26 23:06 ` Michael Steiner
2016-02-26 23:31 ` core dump on rebaseall [attn ocaml maintainer] Marco Atzeri
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=56CE55AD.4060304@cygwin.com \
--to=reply-to-list-only-lh@cygwin.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).