bugMIT/GNU Scheme - Bugs: bug #16387, install failure on Fedora Core 4

 
 

bug #16387: install failure on Fedora Core 4

Submitted by:  None
Submitted on:  Wed 19 Apr 2006 07:59:58 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect behavior
Status: Works For MePrivacy: Public
Assigned to: NoneOriginator Name: Joshua Shinavier
Originator Email: -unavailable-Open/Closed: Closed
Keywords: 

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 03 Jun 2013 04:00:59 PM UTC, comment #2:

I assume the problem was related to our use of mmap and AppArmor. If this bug is not fixed, please let us know.

Matt Birkholz <mhb>
Project Member
Thu 03 Aug 2006 09:47:10 PM UTC, comment #1:

Shouldn't this be listed as crash error, severity high?

I experience this also with Fedora Core 5:
2.6.17-1.2157_FC5 i686 i686 i386 GNU/Linux
gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)

either

> scheme --help

or

> scheme

give output below:
MIT/GNU Scheme running under GNU/Linux
Type `^C' (control-C) followed by `H' to obtain information about interrupts.

>> A hardware fault has occurred within critical section "garbage collector daemon".
>> [signal 11 (SIGSEGV), code 1]
>> Successful recovery is unlikely.

Choose one of the following actions:
D = dump core
I = terminate immediately
N = terminate normally
R = attempt recovery
Q = terminate normally
Action ->

Anonymous
Wed 19 Apr 2006 07:59:58 PM UTC, original submission:

I get a segfault when I invoke the scheme binary built from snapshot 20060414 in FC4. I'm using GCC 4.0.2, which is why I couldn't build from the 7.7.1 package (make failed with "invalid lvalue" errors; see bug #14994). Apparently execution never gets past this function in dump.c:

unsigned long
DEFUN (checksum_area, (start, count, initial_value),
register unsigned long * start
AND register long count
AND unsigned long initial_value)
{
register unsigned long value;

value = initial_value;
while ((--count) >= 0)
value = (value ^ (*start++));
return (value);
}

Output from scheme looks like this:

MIT/GNU Scheme running under GNU/Linux
Type `^C' (control-C) followed by `H' to obtain information about interrupts.

>> A hardware fault has occurred within critical section "garbage collector daemon".
>> [signal 11 (SIGSEGV), code 1]
>> Successful recovery is unlikely.

Choose one of the following actions:
D = dump core
I = terminate immediately
N = terminate normally
R = attempt recovery
Q = terminate normally
Action ->
Aborted

Note: although I chose (D)ump at this point, no dump file was produced.

Originally I tried to use the already-built 7.7.1 scheme binary but likewise got a segfault, but without the message and prompt. Here are the last few lines of GDB output:

Setup_Memory (Our_Heap_Size=285696, Our_Stack_Size=102400,
Our_Constant_Size=714752) at memmag.c:177
177 memmag.c: No such file or directory.
in memmag.c
(gdb)
185 in memmag.c
(gdb)
187 in memmag.c
(gdb)
linux_heap_malloc (requested_length=5554176) at ux.c:640
640 ux.c: No such file or directory.
in ux.c
(gdb)
642 in ux.c
(gdb)

Program received signal SIGSEGV, Segmentation fault.
0x0054d000 in ?? ()
(gdb)
Cannot find bounds of current function

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by mhb (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 03 Jun 2013 04:00:59 PM UTCmhbStatusNone=>Works For Me
      Open/ClosedOpen=>Closed
      Summaryinstall failure (FC4)=>install failure on Fedora Core 4

    Back to the top


    Powered by Savane 3.1-cleanup