From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Please test latest developer snapshot
Date: Sat, 26 Feb 2011 09:51:00 -0000 [thread overview]
Message-ID: <AANLkTi=083fy+qKbyYjwtePq6KO9s05OZ3OcV1y4UccQ@mail.gmail.com> (raw)
In-Reply-To: <4D6844C8.7010801@acm.org>
On Sat, Feb 26, 2011 at 1:09 AM, David Rothenberger wrote:
> On 2/25/2011 3:24 PM, David Rothenberger wrote:
>> I realize this report won't be terribly useful, but I did encounter
>> a problem with the latest snapshot. I have a local git
>> repository. With the snapshot, "git log" produces:
>>
>> 0 [main] git 4944 C:\cygwin\bin\git.exe: *** fatal error - could not load C:\WINDOWS\system32\winmm.dll, Win32 error 487
>>
>> This works fine up through the 20100924 snapshot and starts to fail
>> on the 20100926 snapshot.
>>
>> This only occurs on some of my git repositories. I was not able to
>> reproduce it using the latest snapshot by just making a simple
>> repository, adding a file, then running "git log".
>>
>> This is on Windows XP Pro in case it matters (32-bit, all patches
>> installed).
>>
>> I wish I could be more helpful and provide a test case to reproduce
>> it.
>
> I was able to reproduce this using a clone of the git repository itself:
>
> % uname -a
> CYGWIN_NT-5.1 tela 1.7.8s(0.236/5/3) 20110221 20:36:00 i686 Cygwin
> % git clone git://github.com/git/git.git
> Cloning into git...
> remote: Counting objects: 134689, done.
> remote: Compressing objects: 100% (39672/39672), done.
> remote: Total 134689 (delta 100250), reused 126970 (delta 93150)
> Receiving objects: 100% (134689/134689), 28.44 MiB | 621 KiB/s, done.
> Resolving deltas: 100% (100250/100250), done.
> % cd git/
> % git log
> 0 [main] git 3088 C:\cygwin\bin\git.exe: *** fatal error - could not load C:\WINDOWS\system32\winmm.dll, Win32 error 487
>
>
> --
> David Rothenberger
>
same on XP SP3,
$ uname -a
CYGWIN_NT-5.1 MATZERI-FSC-EU 1.7.8s(0.236/5/3) 20110221 20:36:00 i686 Cygwin
$ git log
10 [main] git 4800 E:\cygwin2\bin\git.exe: *** fatal error -
could not load C:\WINDOWS\system32\winmm.dll, Win32 error 487
Stack trace:
Frame Function Args
0022AEB4 6102785B (0022AEB4, 00000000, 00000000, 00000000)
0022B1A4 6102785B (6117DC60, 00008000, 00000000, 6117F997)
0022C1D4 61004E5B (6117F084, 0022C200, 00000000, 00000000)
0022C434 610013F7 (610EEBC1, 0022C460, 7C90DFCA, 7C8329C8)
0022C478 6115DE2C (6123D0E0, 0022C6FC, 0022C588, 610E9A06)
0022C5E8 610BE3BF (0022C6FC, 0022C660, 0022C640, 0022C620)
0022C748 610BEDC0 (00000001, 0022C770, 0022C6A0, 0022C770)
0022C778 610C2B45 (00000007, 0000003D, 00000001, 61024273)
0022C7E8 00469F57 (0052A490, 0022C868, 0022C848, 00430B15)
0022C7F8 004653FE (0022CC14, 0022C838, 0022C868, 0022CC24)
0022C848 00430B15 (0022C868, 0022CC24, 00610C30, 00610C38)
0022CC38 00430FDA (00000001, 61245B88, 00000000, 0022CCD4)
0022CCE8 004017A9 (612459E4, 004DB17A, 00000000, 00000000)
0022CD48 004019FE (00000000, 00000000, 0022CD88, 61006F68)
0022CD88 61006F68 (00000000, 0022CDC4, 610068B0, 7FFDC000)
End of stack trace
$ cygcheck git
Found: E:\cygwin2\bin\git.exe
E:\cygwin2\bin\git.exe
E:\cygwin2\bin\cygcrypto-0.9.8.dll
E:\cygwin2\bin\cygwin1.dll
C:\WINDOWS\system32\ADVAPI32.DLL
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\RPCRT4.dll
C:\WINDOWS\system32\Secur32.dll
E:\cygwin2\bin\cygz.dll
E:\cygwin2\bin\cyggcc_s-1.dll
E:\cygwin2\bin\cygiconv-2.dll
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:[~2011-02-26 9:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 12:04 Corinna Vinschen
2011-02-17 18:06 ` Ken Brown
2011-02-17 18:15 ` marco atzeri
2011-02-18 12:36 ` Corinna Vinschen
2011-02-18 13:34 ` marco atzeri
2011-02-17 19:33 ` Aaron Peromsik
2011-02-17 20:15 ` Yaakov (Cygwin/X)
2011-02-19 18:29 ` Warren Young
2011-02-19 18:35 ` Warren Young
2011-02-19 20:35 ` Warren Young
2011-02-20 12:16 ` Corinna Vinschen
2011-02-21 14:16 ` Eric Blake
2011-02-21 15:21 ` Thomas Wolff
2011-02-26 0:25 ` Vorfeed Canal
2011-02-26 0:45 ` Eric Blake
2011-02-26 1:03 ` Thomas Wolff
2011-02-27 7:35 ` Vorfeed Canal
2011-02-27 10:21 ` Vorfeed Canal
2011-02-27 11:21 ` Vorfeed Canal
2011-02-24 14:57 ` Chris Sutcliffe
2011-02-24 15:16 ` Corinna Vinschen
2011-02-24 19:34 ` Karl M
2011-02-24 20:56 ` Reini Urban
2011-02-24 21:52 ` Kai Tietz
2011-02-25 9:47 ` Corinna Vinschen
2011-02-25 23:25 ` David Rothenberger
2011-02-26 0:09 ` David Rothenberger
2011-02-26 9:51 ` marco atzeri [this message]
2011-02-26 10:36 ` Corinna Vinschen
2011-02-27 14:15 ` Corinna Vinschen
2011-02-27 18:45 ` David Rothenberger
2011-03-01 7:06 ` Christopher Faylor
2011-03-01 15:51 ` David Rothenberger
2011-02-18 15:34 Angelo Graziosi
2011-02-19 16:05 ` jdzstz - gmail dot com
2011-02-27 15:03 Angelo Graziosi
[not found] <AANLkTim4xT_LL=CGFXhgKmO0gLd5P_rXctaMpHwT2pxn@mail.gmail.com>
2011-03-03 12:22 ` Oleg Marchuk
2011-03-03 12:53 ` Oleg Marchuk
2011-03-03 16:41 ` 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='AANLkTi=083fy+qKbyYjwtePq6KO9s05OZ3OcV1y4UccQ@mail.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).