[ros-kernel] Memory Manager / Loader bug?

[Hartmut Birr]

I get the same result.

- Hartmut

> -----Original Message-----
> From: ros-kernel-bounces at reactos.com 
> [mailto:ros-kernel-bounces at reactos.com] On Behalf Of Filip Navara
> Sent: Friday, January 30, 2004 11:55 PM
> To: ReactOS Kernel List
> Subject: Re: [ros-kernel] Memory Manager / Loader bug?
> 
> 
> Hi,
> 
> you can get the Mozilla Firebird binary I'm using at 
> http://ftp.mozilla.org/pub/mozilla.org/firebird/releases/0.7/M
> ozillaFirebird-0.7-win32.zip. 
> I used the current CVS for testing.
> 
> Regards,
> Filip
> 
> Hartmut Birr wrote:
> 
> >Hi,
> >
> >I've donload mozilla-win32-1.6-installer.exe. I do not see 
> the COW fault
> >error. But I can't install mozilla. I see only a progress box for a
> >short time. Do you use the current cvs tree or the 0.2 
> release? My last
> >commit to section.c is related to the COW bug.
> >
> >- Hartmut
> >
> >  
> >
> >>-----Original Message-----
> >>From: ros-kernel-bounces at reactos.com 
> >>[mailto:ros-kernel-bounces at reactos.com] On Behalf Of Filip Navara
> >>Sent: Friday, January 30, 2004 9:48 PM
> >>To: ReactOS Kernel List
> >>Subject: [ros-kernel] Memory Manager / Loader bug?
> >>
> >>
> >>Hi all!
> >>
> >>I've tried to trace to the long standing bug that it blocker 
> >>for Mozilla 
> >>Firebird and OpenOffice (at least the version I have). 
> While loading 
> >>Mozilla Firebird, it prints
> >>
> >>(mm/section.c:1262) COW fault for page with PESS 0. Address 
> >>was 0x008E1000
> >>(mm/section.c:304) Entry == 0 for MmUnsharePageEntrySectionSegment
> >>
> >>and bugchecks. The access to this page is initiated in 
> >>lib/ntdll/ldr/utils.c, function LdrpProcessImportDirectory. 
> At line ~ 
> >>1502 there is a call to LdrGetExportByName and the return value is 
> >>immediately assigned to *ImportAddressList. That's the place 
> >>where the 
> >>page fault actually happens. Few lines above there is a call to 
> >>NtProtectVirtualMemory that should allow read / write 
> access to this 
> >>memory. The call to NtProtectVirtualMemory should set access 
> >>rights for 
> >>memory range 0x8e0fd8 - 0x8e1038 and so accessing 0x8e1000 
> shouldn't 
> >>cause any problems. Can someone with better knowledge of the loader 
> >>and/or memory manager help me?
> >>
> >>Thanks
> >>Filip
> >>
> >>
> >>_______________________________________________
> >>Ros-kernel mailing list
> >>Ros-kernel at reactos.com
> >>http://reactos.com/mailman/listinfo/ros-kernel
> >>
> >>    
> >>
> >
> >_______________________________________________
> >Ros-kernel mailing list
> >Ros-kernel at reactos.com
> >http://reactos.com/mailman/listinfo/ros-kernel
> >
> >
> >  
> >
> 
> _______________________________________________
> Ros-kernel mailing list
> Ros-kernel at reactos.com
> http://reactos.com/mailman/listinfo/ros-kernel
>