It's not supposed to be that way... maybe we need to check in a new cygwin.

On Thu, Oct 1, 2009 at 4:03 PM, vha14 <vuh...@gmail.com> wrote:
>
> So it looks like I need to install Cygwin separately before I can
> build Chrome? If so this should be added to the Windows build
> instruction page.
>
> On Oct 1, 2:59 pm, Mohamed Mansour <m...@chromium.org> wrote:
>> I run "Cygwin Bash Shell" not from Command Prompt:
>>
>> moha...@mohamed-pc ~$ bash
>>
>>  -Mohamed
>>
>>
>>
>> On Thu, Oct 1, 2009 at 5:32 PM, vha14 <vuh...@gmail.com> wrote:
>>
>> > Hi Mohamed, can you run bash.exe from cmd? I get the following error:
>>
>> > E:\chromium\home\chrome-svn\tarball\chromium\src\third_party\cygwin
>> > \bin>bash
>> >      9 [main] bash 8384 _cygtls::handle_exceptions: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >   9964 [main] bash 8384 open_stackdumpfile: Dumping stack trace to
>> > bash.exe.stackdump
>> >  211065 [main] bash 8384 _cygtls::handle_exceptions: Exception:
>> > STATUS_ACCESS_VIOLATION
>> >  229623 [main] bash 8384 _cygtls::handle_exceptions: Error while
>> > dumping state (probably corrupted stack)
>>
>> > On Oct 1, 2:17 pm, Mohamed Mansour <m...@chromium.org> wrote:
>> > > Windows 7 64bit works fine here (using the default settings from
>> > > dev.chromium.org)  Make sure you have access to the folder your writing
>> > to.
>> > > Some folders require admin mode.
>> > >  -Mohamed
>>
>> > > On Thu, Oct 1, 2009 at 4:10 PM, vha14 <vuh...@gmail.com> wrote:
>>
>> > > > Detailed error message:
>>
>> > > > 1>------ Build started: Project: js2c, Configuration: Debug Win32
>> > > > ------
>> > > > 1>js2c
>> > > > 2>------ Build started: Project: cygwin, Configuration: Debug Win32
>> > > > ------
>> > > > 2>setup_mount
>> > > > 1>     30 [main] bash 8980 _cygtls::handle_exceptions: Exception:
>> > > > STATUS_ACCESS_VIOLATION
>> > > > 1>   3645 [main] bash 8980 open_stackdumpfile: Dumping stack trace to
>> > > > bash.exe.stackdump
>> > > > 2>The operation completed successfully.
>> > > > 2>The operation completed successfully.
>> > > > 1>Project : error PRJ0002 : Error result 35584 returned from 'C:
>> > > > \Windows\SysWow64\cmd.exe'.
>>
>> > > > Content of bash.exe.stackdump:
>>
>> > > > E:\chromium\home\chrome-svn\tarball\chromium\src\chrome>more
>> > > > bash.exe.stackdump
>> > > > Exception: STATUS_ACCESS_VIOLATION at eip=0043AE30
>> > > > eax=00000000 ebx=00000000 ecx=61106EC8 edx=00000000 esi=611021A0
>> > > > edi=0045A3E0
>> > > > ebp=0028CBC8 esp=0028C58C program=e:\chromium\home\chrome-svn\tarball
>> > > > \chromium\s
>> > > > rc\third_party\cygwin\bin\bash.exe, pid 8296, thread main
>> > > > cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>> > > > Stack trace:
>> > > > Frame     Function  Args
>> > > > 0028CBC8  0043AE30  (00000003, 02361C00, 02360090, 772F0000)
>> > > > 0028CD68  610060D8  (00000000, 0028CDA0, 61005450, 0028CDA0)
>> > > > 61005450  61004416  (0000009C, A02404C7, E8611021, FFFFFF48)
>> > > >  431390 [main] bash 8296 _cygtls::handle_exceptions: Exception:
>> > > > STATUS_ACCESS_VI
>> > > > OLATION
>> > > >  509897 [main] bash 8296 _cygtls::handle_exceptions: Error while
>> > > > dumping state (
>> > > > probably corrupted stack)
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to