I don't know what would help, but one thing that usually does is a stack trace. You can probably get it from a coredump file or by something like this:
$ gdb `which racket` [... stuff ...] (gdb) set args -l setup (gdb) run On Wed, Feb 13, 2013 at 10:24 AM, Asumu Takikawa <as...@ccs.neu.edu> wrote: > Hi all, > > I get a reproducible segfault when I built Racket from git HEAD. This is > what I see: > > raco setup: 7 making: redex/examples (Reduction Semantics examples) > reverse: contract violation > expected: list? > given: 4193052015854236082 > > SIGSEGV SI_KERNEL SI_CODE 128 fault on addr (nil) sent by kernel > Aborted > make[1]: *** [install-3m] Error 134 > make[1]: Leaving directory `/home/asumu/plt/racket-git-segfault/src/build' > make: *** [install] Error 2 > > It always seems to segfault at that point in the build. I'm building a > fresh copy of the tree, so it's not a stale zo problem or anything. > > Anything I can do to diagnose? > > Cheers, > Asumu > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
