From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Failure with fork()
Date: Fri, 28 Jun 2013 07:59:00 -0000 [thread overview]
Message-ID: <51CD4177.1040708@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306272257220.27492@enira.zlyna.ubzr>
Il 6/28/2013 8:42 AM, Alan W. Irwin ha scritto:
> I am getting absolutely nowhere.
>
[cut]
>
> I didn't get these hangs a month ago when I tried all this
> before with wine-1.5.19. Instead, at that time I got the exact error
> message when running the above script concerning an unhandled page
> fault that others have described at
> http://bugs.winehq.org/show_bug.cgi?id=24018 and which the fork-fixed
> cygwin1.dll is supposed to fix. So presumably Cygwin's
> bash.exe or some application executed by the above script has
> changed in the last month to cause the different wine symptoms.
> Or I am inadvertently doing something different than I did a month
> ago.
>
> So unless someone can suggest a method to get around the "Can't open
> package database for writing. File exists." message, and assuming
> that method doesn't subsequently run into the script hang (which is a
> big if), then I think it is time for someone with a lot more wine and
> cygwin expertise than me to take over here to attempt to try and
> figure out a way to run setup.exe on Wine with fork-fixed cygwin1.dll
> overwriting the buggy version.
>
> Alan
Hi Alan,
I assume you are not testing on wine for fun, but cygwin on wine
seems a real problem as the bug can be in any of the two platforms.
Could you clarify the original scope ?
Eventually we can test in your behalf.
As alternative to wine, if I am not wrong, Corinna when testing cygwin
on several platforms (32/64, XP, W7, W8 , Server...) is using some VM
and also her main compiling machine is a Linux one;
setup.exe itself is cross-compiled on a Linux machine.
Eventually it is a more easy approuch for your trials
Regards
Marco
--
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:[~2013-06-28 7:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 7:55 Alan W. Irwin
2013-06-28 7:59 ` marco atzeri [this message]
2013-06-28 8:52 ` Corinna Vinschen
2013-06-28 10:16 ` gmt
2013-06-28 10:20 ` Corinna Vinschen
2013-06-28 19:05 ` Alan W. Irwin
2013-07-04 20:39 ` Failure with fork() (Cygwin on Wine install now sort of works) Alan W. Irwin
2013-07-05 19:30 ` Alan W. Irwin
2013-07-05 21:25 ` Christopher Faylor
2013-06-28 8:42 ` Failure with fork() Alan W. Irwin
2013-06-28 9:40 ` gmt
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 18:58 Alan W. Irwin
2013-06-27 19:01 ` marco atzeri
2013-06-27 19:45 ` Alan W. Irwin
2013-06-27 20:17 ` Achim Gratz
2013-06-27 20:33 ` gmt
2013-06-27 19:13 ` Alan W. Irwin
2013-06-27 19:15 ` marco atzeri
2013-06-27 20:43 ` Alan W. Irwin
2013-06-27 20:47 ` Christopher Faylor
2013-06-27 20:48 ` Larry Hall (Cygwin)
2013-06-27 20:56 ` Thrall, Bryan
2013-06-28 1:28 ` Larry Hall (Cygwin)
2013-06-27 20:55 ` Peter Rosin
2013-06-27 21:52 ` Yaakov (Cygwin/X)
2013-06-27 21:58 ` Alan W. Irwin
2013-06-27 21:59 ` Yaakov (Cygwin/X)
2013-06-28 9:19 ` Corinna Vinschen
2013-06-27 10:49 Arjen Markus
2013-06-27 11:27 ` Ryan Johnson
2013-06-27 11:29 ` Corinna Vinschen
2013-06-27 12:19 ` Arjen Markus
2013-06-27 17:01 ` Corinna Vinschen
2013-06-27 17:03 ` Christopher Faylor
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=51CD4177.1040708@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).