subject:"\[racket\] Racket 5.2.1 segfault"

Re: [racket] Racket 5.2.1 segfault

2012-03-01 Thread Simon Haines

On 1 March 2012 17:16, Kevin Tew wrote: > This is the magic incantation I use to use with valgrind. > > valgrind --tool=memcheck --db-attach=yes > --vex-iropt-precise-memory-exns=yes --leak-check=full --num-callers=40 > > Thanks Kevin, I retried my test with your options, but had the same result

Re: [racket] Racket 5.2.1 segfault

2012-02-29 Thread Kevin Tew

This is the magic incantation I use to use with valgrind. valgrind --tool=memcheck --db-attach=yes --vex-iropt-precise-memory-exns=yes --leak-check=full --num-callers=40 the --vex-iropt-precise-memory-exns=yes is important for running racket. Kevin On 02/29/2012 10:29 PM, Simon Haines wrote:

[racket] Racket 5.2.1 segfault

2012-02-29 Thread Simon Haines

I'm coming across a segfault when using racket 5.2.1 in some particular circumstances. Here is a sample to reproduce the problem: #!/home/simon/racket/bin/racket #lang racket/base (display "This is a test, designed to provoke an emotional response") When I chmod +x and run it, it runs just fine: