Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Steven Wu
I stopped in the function, and it seems to be correct. I checked to the map, and the value was right, it wasn't NULL. I tried to stop in strncmp and see what that parameters were. Wasn't very successful the first tried. I haven't used gdb for a while, and need to refresh it. steve On Mar 5, 20

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Hans Aberg
On 5 Mar 2011, at 22:25, Andy Wingo wrote: > On Sat 05 Mar 2011 18:27, Steven Wu writes: > >> #0 0x7fff83bec7f0 in strncmp () >> #1 0x0001019e9684 in init_bouncing_parens [inlined] () at >> /Users/wus/local/src/gnu/guile-2.0.0/guile-readline/readline.c:445 ... > Are you certain you ar

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Andy Wingo
On Sat 05 Mar 2011 18:27, Steven Wu writes: > #0 0x7fff83bec7f0 in strncmp () > #1 0x0001019e9684 in init_bouncing_parens [inlined] () at > /Users/wus/local/src/gnu/guile-2.0.0/guile-readline/readline.c:445 This function is defined as follows: static void init_bouncing_parens (

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Hans Aberg
On 5 Mar 2011, at 21:14, Steven Wu wrote: > My is also MacOS X 10.6.6, the kernel version is 10.6.0 which is what uname > will gives. It seems like readline issue. and I am debugging it now. Some seem to have problems with that, but readline-6.1 works for me. I just did ./configure && make. Ha

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Steven Wu
Thanks, I'll give it a try. steve On Mar 5, 2011, at 12:52 PM, Michael Ellis wrote: > On Sat, Mar 5, 2011 at 12:27 PM, Steven Wu wrote: >> I built guile-2.0.0 from the tarball, and when I started it, it crashed. >> > >> Program received signal EXC_BAD_ACCESS, Could not access memory. >> Reason

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Steven Wu
My is also MacOS X 10.6.6, the kernel version is 10.6.0 which is what uname will gives. It seems like readline issue. and I am debugging it now. steve On Mar 5, 2011, at 12:41 PM, Hans Aberg wrote: > On 5 Mar 2011, at 18:27, Steven Wu wrote: > >> I built guile-2.0.0 from the tarball, and when

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Michael Ellis
On Sat, Mar 5, 2011 at 12:27 PM, Steven Wu wrote: > I built guile-2.0.0 from the tarball, and when I started it, it crashed. > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_INVALID_ADDRESS at address: 0x01a17070 > 0x7fff83bec7f0 in strncmp () > (gdb

Re: guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Hans Aberg
On 5 Mar 2011, at 18:27, Steven Wu wrote: > I built guile-2.0.0 from the tarball, and when I started it, it crashed. > > The config option: > $./config.status --config '--enable-error-on-warning' '--disable-deprecated' > '--prefix=/usr' Note that on BSD systems (as Mac OS X), /usr/ without /usr/

Re: Missing and out-of-date information in guile.1, the Guile man page

2011-03-05 Thread Andy Wingo
Hi Mark, On Sat 05 Mar 2011 01:45, Mark Harig writes: > On Fri, Mar 04, 2011 at 10:35:50AM +0100, Andy Wingo wrote: >> On Tue 25 Jan 2011 08:05, Mark Harig writes: >> >> > On Mon, Jan 24, 2011 at 10:54:56PM +0100, Andy Wingo wrote: >> >> >> >> I updated the man page. I don't really know groff

guile-2.0.0 crash when started on MacOS X 10.6.0

2011-03-05 Thread Steven Wu
I built guile-2.0.0 from the tarball, and when I started it, it crashed. The config option: $./config.status --config '--enable-error-on-warning' '--disable-deprecated' '--prefix=/usr' --- here is the bt from running guile $ gdb /usr/bin/guile run Program received signal EXC_BAD_ACCESS, Could not

Re: Mac OS X .dylib not working

2011-03-05 Thread Peter O'Gorman
On 03/04/2011 01:00 PM, Peter O'Gorman wrote: On 03/04/2011 12:47 PM, Ralf Wildenhues wrote: +if test "$shlibpath_var" = PATH; then This looks wrong; shouldn't it be != here? Otherwise, ... Looking at the original test, the above is correct there - it wants to avoid messing with PATH on W