[webkit-dev] prepare-Changelog crashing on cygwin

Eric Seidel eric at webkit.org
Mon May 10 13:07:57 PDT 2010


Is this caused by the base load address of both perl and svn
conflicting/overlapping?  (I don't really know how CYGWIN works.)

Is this something we should detect in our scripts and warn about?

On Mon, May 10, 2010 at 12:41 PM, John Abd-El-Malek <jam at google.com> wrote:
> btw, I finally solved this.  credit to tonyg:
> 1) close cygwin
> 2) C:\cygwin\bin>ash rebaseall
>
> On Mon, May 10, 2010 at 12:20 PM, Eric Seidel <eric at webkit.org> wrote:
>>
>> On Mon, May 10, 2010 at 11:31 AM, Eric Seidel <eseidel at google.com> wrote:
>> > I have seen this on the win-ews ec2 instance.
>> >
>> > On May 10, 2010 1:35 PM, "John Abd-El-Malek" <jam at google.com> wrote:
>> >
>> > After reimaging my Windows 7 machine, prepare-Changelog always crashes
>> > for
>> > me now.  It seems to have problems running "svn diff".  I installed
>> > cygwin
>> > through the installer on webkit.org.  I don't have any anti-virus
>> > programs
>> > running, and DEP is turned off for cygwin.exe and svn.exe.  Has anyone
>> > else
>> > seen this?
>> >
>> > Thanks,
>> > John
>> >
>> > jabdelmalek at JABDELMALEK0-W /cygdrive/d/WebKit/WebKit/chromium
>> > $ ../../WebKitTools/Scripts/prepare-ChangeLog
>> >   Running status to find changed, added, or removed files.
>> > ?       svn.exe.stackdump
>> >   Reviewing diff to determine which lines changed.
>> >       0 [main] svn 1652 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1873 [main] svn 1652 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 1652 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1873 [main] svn 1652 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 7828 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >       0 [main] svn 7828 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION   1863 [main] svn 7828 open_stackdumpfile:
>> > Dumping
>> > stack trace
>> >  to svn.exe.stackdump
>> >    1863 [main] svn 7828 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 6132 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1818 [main] svn 6132 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 6132 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1818 [main] svn 6132 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       1 [main] svn 15284 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1547 [main] svn 15284 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       1 [main] svn 15284 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1547 [main] svn 15284 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 9296 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    2474 [main] svn 9296 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >    2474 [main] svn 9296 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 10444 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    2067 [main] svn 10444 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 10444 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    2067 [main] svn 10444 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 12428 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1925 [main] svn 12428 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 12428 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1925 [main] svn 12428 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 3940 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >       0 [main] svn 3940 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION   1538 [main] svn 3940 open_stackdumpfile:
>> > Dumping
>> > stack trace
>> >  to svn.exe.stackdump
>> >    1538 [main] svn 3940 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 15008 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    2251 [main] svn 15008 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >    2251 [main] svn 15008 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 14496 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1796 [main] svn 14496 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> >       0 [main] svn 14496 exception::handle: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >    1796 [main] svn 14496 open_stackdumpfile: Dumping stack trace to
>> > svn.exe.stackdump
>> > exec of 'diff' failed: Bad addresssvn: 'diff' returned 255
>> >   Extracting affected function names from source files.
>> >   Change author: John Abd-El-Malek <jam at chromium.org>.
>> >   Running 'svn update' to update ChangeLog files.
>> >     At revision 59081.
>> >   Editing the ./ChangeLog file.
>> > -- Please remember to include a detailed description in your ChangeLog
>> > entry. --
>> > -- See <http://webkit.org/coding/contributing.html> for more info --
>> >
>> > _______________________________________________
>> > webkit-dev mailing list
>> > webkit-dev at lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> >
>> >
>
>


More information about the webkit-dev mailing list