[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-mit-scheme] [bug #36757] Microcode seg faults under 64-bit NetBSD 5

From: Henry Wu
Subject: [Bug-mit-scheme] [bug #36757] Microcode seg faults under 64-bit NetBSD 5.1.2 (amd64)
Date: Sat, 30 Jun 2012 19:32:32 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0


                 Summary: Microcode seg faults under 64-bit NetBSD 5.1.2
                 Project: MIT/GNU Scheme
            Submitted by: mhwu
            Submitted on: Sat 30 Jun 2012 03:32:32 PM EDT
                Category: microcode
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect behavior
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any



The microcode immediately quits upon invocation with a segmentation fault
under the captioned OS.

Upon further investigation, it is system function mmap called with MAP_FIXED
that seg faults.  Calling code is in memmag.c -> ux.c

If I force mmap never to be called with MAP_FIXED (letting the surrounding
code return failure rather than letting it fault), then the runtime tries to
start, but immediately quits within Scheme reporting: "SIGSEGV ... Address not
mapped to object ..." and then end of stream without further chance to
interact.  But the runtime ran enough to print [error] prompts and such.

I don't immediately understand how the current C memory allocation scheme
works to know how to proceed further to debug ... but from a cursory glance,
MAP_FIXED should be allowed to fail like the way I forced it and the system
should still recover.



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]