---

De : Aleksey Bragin <aleksey@reactos.org>
À : ReactOS Development List <ros-dev@reactos.org>
Envoyé le : Mercredi 6 juin 2012 14h45
Objet : [ros-dev] Debug log problems

Hello,
it's time for my periodical rant about debug log mess again. The example below is made using latest VirtualBox 3.

3. What happened to the floppy driver?
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:1579) '\Driver\FLOPPY' initialization failed, status (0xc000000e)
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:61) Deleting driver object '\Driver\FLOPPY'
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:87) HACK: Not unloading the driver image due to critical bugs!
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:1961) IopInitializeDriver() failed (Status c000000e)
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:935) Leaking driver: floppy.sys

Fix it? Don't enable it in trunk builds if it's buggy and not fixed?

All that resulted from my desire to just compare logs attached to the bug report. New log is totally unreadable, I had to spend time figuring out where actually that Live Essentials app was started, what problems it shows, etc.


Best regards,
Aleksey.


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev