From: "E. Madison Bray" <erik.m.bray@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Flask app no longer working from cygwin when set to developer mode
Date: Fri, 25 Jan 2019 09:59:00 -0000 [thread overview]
Message-ID: <CAOTD34YJ=GxtL=Mqj_Ws=1x+FzNA2pctAmhKJUs8ZcFHHTLLKg@mail.gmail.com> (raw)
In-Reply-To: <BYAPR07MB4632F57C3599D28D92711057DB9A0@BYAPR07MB4632.namprd07.prod.outlook.com>
On Thu, Jan 24, 2019 at 9:45 PM Maxim Kupfer wrote:
>
> This problem occurred immediately after attempting to run my python flask app in the backround (i.e $python app.py &)
>
> It gave me the following error:
> 2 [main] python3.6m 11340 child_info_fork::abort: unable to remap _lbfgsb.cpython-36m-x86_64-cygwin.dll to same address as parent (0x4930000) - try running rebaseall
>
> I've tried rebasing and restarting, but both didn't fix anything. The app works fine when it is not in developer mode, but then I don't get hot reloading. The app also works from my windows command line, so that is my temporary fix for now, but I would love to get my precious Cygwin setup up an running again.
>
> Thanks for the help!
Are you by any chance using a virtualenv or something like that? It
looks like your app is using some compiled extension modules. I'm not
sure exactly where _lbfgsb.*.dll comes from--possibly Numpy or Scipy?
It's never been entirely clear to me exactly how rebase searches for
files, but I think by default it might only take into account DLLs
installed by Cygwin packages. So if you have some DLLs in a
virtualenv, for example, you have to manually include them. I'll
typically do something like:
$ find path/to/virtualenv -type f -name '*.dll' -print > dlls-to-rebase.txt
$ rebase -O -T dlls-to-rebase.txt
--
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:[~2019-01-25 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 20:45 Maxim Kupfer
2019-01-25 9:59 ` E. Madison Bray [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='CAOTD34YJ=GxtL=Mqj_Ws=1x+FzNA2pctAmhKJUs8ZcFHHTLLKg@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).