There's a script in the 'meta' directory of the Guile sources called 'gdb-uninstalled-guile'. I believe it sets up whatever environment variables need setting and then calls gdb for you. I've used it to debug Guile in the past.
Thanks a lot for tracking down this bug Noah Lavine On Wed, Jan 9, 2013 at 10:39 PM, Nala Ginrut <nalagin...@gmail.com> wrote: > On Wed, 2013-01-09 at 21:59 -0500, Peter Teeson wrote: > > Greetings: > > Mac Pro 4,1 - MacOS 10.7.5 > > I filed bug <http://bugs.gnu.org/13342> and Ludo' invited me to > investigate which I've been doing, > > including reading the other bugs on this problem > http://bugs.gnu.org/10015, http://bugs.gnu.org/10681. > > > > My conclusion at this time, after a number of experiments, is that the > issue is not in the llvm compiler but somewhere in the interpreter. > > I am not familiar with the scheme or guile languages but have been a > (now retired) developer on Mac for 25 years. > > Before that 14 years on IBM mainframes as a systems programmer working > on an APL interpreter. > > > > I would like to try and track down this old issue but don't know how to > debug the scheme/guile interpreter. > > Looked in the guile manual but didn't find anything that helped me. > > > > Please give me some pointers on how to proceed. > > > > TIA > > > > Peter > > hi Peter! > I know nothing about that bug. But if you want to use GDB to debug with > Guile code, you may need 'gdbinit' which is in the toplevel guile src > directory. > Say, 'gdb -x gdbinit', then you can use 'gwrite' to print out the SCM > type vars's value for your debugging. > > > > > >
