[racket] Exception Stack Trace Troubles

From: Chad Albers (calbers at neomantic.com)
Date: Wed Jun 27 07:34:58 EDT 2012

Hi Eli,

Here's the file that I'm running in a gist: https://gist.github.com/3003496

In other words, it's a cut-and-paste of code that you posted earlier
in this chain:

#lang racket
(with-handlers ([void (λ (e)
                          (exn-continuation-marks e)))])
   (+ 1 "two"))

Let's say the file is called "example.rkt".  I execute this file using
the CLI as follows:  racket example.rkt.

That's it.  I'm running Debian linux on 64 bit architecture.  I've
checked the Debian bug reports on racket, and nothing similar has been

Thanks again for your help,


Chad Albers

On Wed, Jun 27, 2012 at 2:00 AM, Eli Barzilay <eli at barzilay.org> wrote:
> Two days ago, Michael Wilber wrote:
> > If I understand correctly, by default, Racket doesn't provide forms
> > with stack trace information when running from the CLI by
> > default.
> It does (and I tried my examples on both racket and drracket).
> > Does it work from within DrRacket? If so, look into the errortrace
> > module, or add (require errortrace) to the top of the .rkt, or run
> > it like this: racket -l errortrace test.rkt
> The purpose of errortrace is to provide a more accurate stacktrace
> (and originally, to provide a trace when mzscheme didn't have one).
> 9 hours ago, Chad Albers wrote:
> > I'm using Debian Linux.
> I tried it now with our debian build (which is an x86_64 build), and
> it worked.
> 9 hours ago, Chad Albers wrote:
> > It doesn't produce a stack trace of DrRacket.
> >
> > Also, it doesn't produce a stack trace if I include the errortrace
> > on the command line.
> Can you post the exact file that you tried and how you ran it?
> --
>          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
>                    http://barzilay.org/                   Maze is Life!

Posted on the users mailing list.