[Sbcl-devel] Bus Error when running SBCL on Mac

[Tim McKeaveney]

Downloaded latest binary dist. (1.0.23) to:
/Users/tmck/lisp/SBCL/

Run check by:
$ sh run-sbcl.sh
(running SBCL from: .)
run-sbcl.sh: line 35: 489 Bus error
SBCL_HOME="$BASE"/contrib "$BASE"/src/runtime/sbcl --core
"$BASE"/output/sbcl.core "$@"

I'm running Mac OS X 10.4.11, Intel Core 2 Duo.
I don't have admin priveleges, so I'm trying to run it in my home
directory first.

Anything I've missed?

Regards,
Timbo

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Sbcl-devel mailing list
Sbcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-devel

[Nikodemus Siivola]

On Wed, Dec 17, 2008 at 5:55 AM, Tim McKeaveney <macoo...@gmail.com> wrote:

> Downloaded latest binary dist. (1.0.23) to:
> /Users/tmck/lisp/SBCL/
>
> Run check by:
> $ sh run-sbcl.sh
> (running SBCL from: .)
> run-sbcl.sh: line 35: 489 Bus error
> SBCL_HOME="$BASE"/contrib "$BASE"/src/runtime/sbcl --core
> "$BASE"/output/sbcl.core "$@"
>
> I'm running Mac OS X 10.4.11, Intel Core 2 Duo.

What does

src/runtime/sbcl --core output/sbcl.core

do when in the SBCL directory?

Exactly which package did you download? Both

http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-darwin-binary.tar.bz2
http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-64-darwin-binary.tar.bz2

work for me on 10.5.5 using run-sbcl.sh. I can try on a 10.4 box later today.

Cheers,

-- Nikodemus

[Brian Mastenbrook]

On Dec 17, 2008, at 8:18 AM, Nikodemus Siivola wrote:

> What does
>
> src/runtime/sbcl --core output/sbcl.core
>
> do when in the SBCL directory?
>
> Exactly which package did you download? Both
>
> http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-darwin-binary.tar.bz2
> http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-64-darwin-binary.tar.bz2
>
> work for me on 10.5.5 using run-sbcl.sh. I can try on a 10.4 box
> later today.

Several users have reported trouble running binaries built under
Leopard on Tiger systems. I no longer have any 10.4 machines, so I'd
appreciate any clues you could find.
--
Brian Mastenbrook
br...@mastenbrook.net
http://brian.mastenbrook.net/

[Nikodemus Siivola]

On Wed, Dec 17, 2008 at 5:05 PM, Brian Mastenbrook
<br...@mastenbrook.net> wrote:

> Several users have reported trouble running binaries built under Leopard on
> Tiger systems.

Right, but I wasn't aware of any issues post 1.0.21.12.

> I no longer have any 10.4 machines, so I'd appreciate any
> clues you could find.

Will do. If nothing else, I can at least provide a 10.4 compatible binary.

Cheers,

-- Nikodemus

[Nathan Froyd]

On Wed, Dec 17, 2008 at 9:18 AM, Nikodemus Siivola
<niko...@random-state.net> wrote:
> On Wed, Dec 17, 2008 at 5:55 AM, Tim McKeaveney <macoo...@gmail.com> wrote:
>> Downloaded latest binary dist. (1.0.23) to:
>> /Users/tmck/lisp/SBCL/
>>
>> Run check by:
>> $ sh run-sbcl.sh
>> (running SBCL from: .)
>> run-sbcl.sh: line 35: 489 Bus error
>> SBCL_HOME="$BASE"/contrib "$BASE"/src/runtime/sbcl --core
>> "$BASE"/output/sbcl.core "$@"
>>
>> I'm running Mac OS X 10.4.11, Intel Core 2 Duo.
>
> What does
>
> src/runtime/sbcl --core output/sbcl.core
>
> do when in the SBCL directory?
>
> Exactly which package did you download? Both
>
> http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-darwin-binary.tar.bz2
> http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.23-x86-64-darwin-binary.tar.bz2
>
> work for me on 10.5.5 using run-sbcl.sh. I can try on a 10.4 box later today.

I can confirm that the 1.0.23 binary packages fall over on a 10.4 box.

-Nathan

[Nathan Froyd]

On Wed, Dec 17, 2008 at 11:16 AM, Nathan Froyd <fro...@gmail.com> wrote:
> I can confirm that the 1.0.23 binary packages fall over on a 10.4 box.

GDB says:

(gdb) handle SIGUSR1 pass nostop
Signal Stop Print Pass to program Description
SIGUSR1 No Yes Yes User defined signal 1
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program:
/Users/froydnj/testing/sbcl-1.0.23-x86-darwin/src/runtime/sbcl --core
output/sbcl.core

Program received signal SIGUSR1, User defined signal 1.

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x9010c802 in _malloc_initialize ()
(gdb) where
#0 0x9010c802 in _malloc_initialize ()
#1 0x900028d7 in malloc ()
#2 0x000097a8 in successful_malloc ()
#3 0x000097db in copied_string ()
#4 0x0000c75e in os_get_runtime_executable_path ()
#5 0x000099c4 in main ()
(gdb)

[Nikodemus Siivola]

On Wed, Dec 17, 2008 at 6:16 PM, Nathan Froyd <fro...@gmail.com> wrote:

> I can confirm that the 1.0.23 binary packages fall over on a 10.4 box.

Does this one work (build on Leopard)?

http://random-state.net/tmp/sbcl-1.0.23.46.tiger-binary.tar.gz

The difference is putting the -mmacosx-version-min=10.4 to LINKFLAGS as well.

ndex: src/runtime/Config.x86-darwin
===================================================================
RCS file: /cvsroot/sbcl/sbcl/src/runtime/Config.x86-darwin,v
retrieving revision 1.6
diff -u -r1.6 Config.x86-darwin
--- src/runtime/Config.x86-darwin 9 Oct 2008 00:36:09 -0000 1.6
+++ src/runtime/Config.x86-darwin 17 Dec 2008 16:43:23 -0000
@@ -10,6 +10,7 @@
# files for more information.

CFLAGS = -g -Wall -O2 -fdollars-in-identifiers -mmacosx-version-min=10.4
+LINKFLAGS += -mmacosx-version-min=10.4
OS_SRC = bsd-os.c x86-bsd-os.c darwin-os.c x86-darwin-os.c
darwin-dlshim.c darwin-langinfo.c
OS_LIBS = -lSystem -lc -ldl
ifdef LISP_FEATURE_SB_THREAD

Cheers,

-- Nikodemus

[Nathan Froyd]

On Wed, Dec 17, 2008 at 11:45 AM, Nikodemus Siivola
<niko...@random-state.net> wrote:
> On Wed, Dec 17, 2008 at 6:16 PM, Nathan Froyd <fro...@gmail.com> wrote:
>
>> I can confirm that the 1.0.23 binary packages fall over on a 10.4 box.
>
> Does this one work (build on Leopard)?
>
> http://random-state.net/tmp/sbcl-1.0.23.46.tiger-binary.tar.gz
>
> The difference is putting the -mmacosx-version-min=10.4 to LINKFLAGS as well.

Yes, that works much better.

-Nathan

[Nikodemus Siivola]

On Wed, Dec 17, 2008 at 7:09 PM, Nathan Froyd <fro...@gmail.com> wrote:
> On Wed, Dec 17, 2008 at 11:45 AM, Nikodemus Siivola
> <niko...@random-state.net> wrote:
>> On Wed, Dec 17, 2008 at 6:16 PM, Nathan Froyd <fro...@gmail.com> wrote:
>>
>>> I can confirm that the 1.0.23 binary packages fall over on a 10.4 box.
>>
>> Does this one work (build on Leopard)?
>>
>> http://random-state.net/tmp/sbcl-1.0.23.46.tiger-binary.tar.gz
>>
>> The difference is putting the -mmacosx-version-min=10.4 to LINKFLAGS as well.
>
> Yes, that works much better.

Committed as 1.0.23.47.

Cheers,

-- Nikodemus

[Brian Mastenbrook]

On Dec 17, 2008, at 11:13 AM, Nikodemus Siivola wrote:

> On Wed, Dec 17, 2008 at 7:09 PM, Nathan Froyd <fro...@gmail.com>
> wrote:
>> On Wed, Dec 17, 2008 at 11:45 AM, Nikodemus Siivola
>> <niko...@random-state.net> wrote:
>>> On Wed, Dec 17, 2008 at 6:16 PM, Nathan Froyd <fro...@gmail.com>
>>> wrote:
>>>
>>>> I can confirm that the 1.0.23 binary packages fall over on a 10.4
>>>> box.
>>>
>>> Does this one work (build on Leopard)?
>>>
>>> http://random-state.net/tmp/sbcl-1.0.23.46.tiger-binary.tar.gz
>>>
>>> The difference is putting the -mmacosx-version-min=10.4 to
>>> LINKFLAGS as well.
>>
>> Yes, that works much better.

Thanks Nikodemus! Somehow I did not realize that what was in CFLAGS
wasn't passed to the linker, and thought it was working because I did
not see any more _open$UNIX2003 symbols in the output from nm.

--
Brian Mastenbrook
br...@mastenbrook.net
http://brian.mastenbrook.net/

[Tim McKeaveney]

Thanks all.

http://random-state.net/tmp/sbcl-1.0.23.46.tiger-binary.tar.gz. seems to work.

Timbo