I see that we have --enable-backtrace option available. there are 2 binaries created in $BUILD/racket/
1. racket3m 2. racketcgc are these standalone binaries for the racket interpreter using different GCs? I'm able to set breakpoints using these, but this is NOT interpreting any of the rkt source files. would appreciate if someone can point me to any docs, that help me the directory structure and design docs for the racket runtime and how to debug/understand the runtime. Thanks. On Monday, August 17, 2015 at 6:54:12 AM UTC-7, tori wrote: > > Hi, > > > I'm planning on studying the racket runtime (JIT, memory management) code. > I'll be reading the source code, in addition to which I wanted to build a > racket system with debugs enabled, so that I can used "lldb" to track the > execution as it happens. > > > I've used the following config to build the system. Can someone please let > me know the right options or if I missed something? > > > ../configure CFLAGS=-g --prefix=SOME_DIR_ABS_PATH --enable-macprefix -- > enable-noopt > > > after installing, I see the following. > > > $ lldb bin/racket > > > > (lldb) break set -n main > > Breakpoint 1: no locations (pending). > > WARNING: Unable to resolve breakpoint to any actual locations. > > (lldb) r > > Process 24130 launched: '../refcode/racket/racket/src/build/bin/racket' ( > x86_64) > > > > Welcome to Racket v6.2.900.10. > > > > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/76b543a9-b2ec-4170-9fdf-d472fc192115%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
