https://bugzilla.novell.com/show_bug.cgi?id=358609


           Summary: IEClone hangs on startup on SLED 10 SP1
           Product: Mono: Class Libraries
           Version: 1.9.0
          Platform: i586
        OS/Version: SLED 10
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Windows.Forms
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [email protected]
          Found By: Component Test


Description of Problem:
IEClone doesn't startup on SLED 10 SP1. When you run it, it just outputs this,
and then sits there indefinitely:

[EMAIL PROTECTED]:~> IEClone
*** glibc detected *** mono: malloc(): memory corruption: 0x089b0840 ***




If you run it in strace, you get this (this is just the end):

futex(0xb7fb0c88, FUTEX_WAKE, 1)        = 0
mprotect(0xb5c72000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0xb5c9a000, 8192, PROT_READ|PROT_WRITE) = 0
futex(0xb5c00010, FUTEX_WAKE, 1)        = 1
futex(0x25f04, FUTEX_WAIT, 2, NULL)     = 0
futex(0x25f04, FUTEX_WAKE, 1)           = 0
mprotect(0xb5c83000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
futex(0x25f04, FUTEX_WAIT, 2, NULL)     = 0
futex(0x25f04, FUTEX_WAKE, 1)           = 0
mprotect(0xb5c87000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC*** glibc detected ***
mono: malloc(): memory corruption: 0x0896e568 ***
) = 0
mprotect(0xb5c87000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0xb5c87000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0xb5c84000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0xb5c84000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
futex(0xb7ee9140, FUTEX_WAIT, 2, NULL    


Steps to reproduce the problem:
1. Run IEClone on SLED 10 SP1 i586
2. Notice the memory corruption error as above.


Actual Results:
Hangs on start


Expected Results:
It should start up.


How often does this happen? 
Every time.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to