Why don't 0.2.8 display filenames and line numbers in stack traces?
Casper
-----Original Message----- From: ros-bugs-bounces@reactos.org [mailto:ros-bugs-bounces@reactos.org] On Behalf Of ReactOS.Bugzilla@reactos.org Sent: 2. november 2005 10:49 To: ros-bugs@reactos.com Subject: [ros-bugs] [Bug 948] New: ReactOS Hangs After Changing ISO Images
http://www.reactos.org/bugzilla/show_bug.cgi?id=948
Summary: ReactOS Hangs After Changing ISO Images Product: ReactOS Version: 0.2.8 Platform: VMWare 5 OS/Version: Microsoft Windows NT 4.0 Status: NEW Severity: major Priority: P3 Component: Kernel AssignedTo: ros-bugs@reactos.com ReportedBy: the80sphreak@yahoo.co.uk QAContact: ros-bugs@reactos.comHi there,
I am using ReactOS inside vmware 5.0 on a Pentium 4 (2GHZ) laptop with 768MB Ram, 20GB Hard disk and windows XP Home + SP2. During my testing of ReactOS 0.2.8, I unmounted one CD image, and mounted another. This caused ReactOS to hang and VMWare to report the processor being halted by the guest OS. I tried a reboot, but this did not help, and now any time I try and access CDs (physical or ISO,) ReactOS hangs with a BSOD.
I have posted 2 screenshots on my website at:
http://www.geocities.com/the80sphreak/reactos.jpg http://www.geocities.com/the80sphreak/reactos2.jpg
If you require any more information, please send me an email at:
the80sphreak@yahoo.co.uk
Thanks,
R. McLay
-- Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Ros-bugs mailing list Ros-bugs@reactos.org http://www.reactos.org/mailman/listinfo/ros-bugs
From: Casper Hornstrup
Why don't 0.2.8 display filenames and line numbers in stack traces?
If you run a release build, symbol information is by default not loaded, so it's not possible to retrieve that info. You need to boot a release build with /LOADSYMBOLS to force the symbols to be loaded.
GvG
How about adding this information to the BSOD? I'm sure most users don't know that and we have to tell them to redo the screenshots each time.
Casper
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Ge van Geldorp Sent: 2. november 2005 17:02 To: 'ReactOS Development List' Subject: RE: [ros-dev] [Bug 948] New: ReactOS Hangs AfterChanging ISO Images
From: Casper Hornstrup
Why don't 0.2.8 display filenames and line numbers in stack traces?
If you run a release build, symbol information is by default not loaded, so it's not possible to retrieve that info. You need to boot a release build with /LOADSYMBOLS to force the symbols to be loaded.
GvG
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev