[Mono-bugs] [Bug 503989] New: Debugger does not work when NX flag (Intel XD bit) is disabled in BIOS settings.
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu May 14 14:06:13 EDT 2009
http://bugzilla.novell.com/show_bug.cgi?id=503989
Summary: Debugger does not work when NX flag (Intel XD bit) is
disabled in BIOS settings.
Classification: Mono
Product: Mono: Debugger
Version: unspecified
Platform: x86-64
OS/Version: openSUSE 11.0
Status: NEW
Severity: Normal
Priority: P5 - None
Component: cli
AssignedTo: martin at novell.com
ReportedBy: krottmayer.johannes at inode.at
QAContact: mono-bugs at lists.ximian.com
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.10)
Gecko/2009042700 SUSE/3.0.10-1.1 Firefox/3.0.10
MDB does not work when Intel XD bit is disabled in BIOS settings.
Reproducible: Always
Steps to Reproduce:
AMI BIOS (Mainboard: ECS Elitegroup P35T-A, CPU: Intel Core 2 Quad Q6600):
Disable "Intel XD bit" under "Advanced Options" in BIOS settings.
NX Flag (Intel XD Bit) disabled:
$ mdb HelloMono.exe
Mono Debugger
(mdb) r
Starting program: HelloMono.exe
Thread @1 stopped at #0: 0x7fffae3d5da1.
0x7fffae3d5da1 add %al,(%rax)
(mdb) c
Thread @1 received signal 11 at #0: 0x7fffae3d5da1.
0x7fffae3d5da1 add %al,(%rax)
(mdb) c
Stacktrace:
Native stacktrace:
/usr/bin/mono [0x47f7b1]
/usr/bin/mono [0x4af74d]
/lib64/libpthread.so.0 [0x7f04a54afb30]
[0x7fffae3d5da1]
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Thread @1 received signal 6 at #0: 0x7f04a4f245c5 in raise+0x35.
0x7f04a4f245c5 cmp $0xfffffffffffff000,%rax
(mdb) c
Thread @1 died with fatal signal 6.
(mdb) Thread @1 exited.
Process #1 exited.
Target exited.
ERROR: No target.
(mdb) q
$
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list