[mcclim-devel] Debugging tips
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How do I maximise the debuggability of mcclim? I'm going back to my mcclim texture generator app, this time using the gtk backend, hoping to stress it a bit. I'm using sbcl-0.9.16. & SLIME Does anyone have any debugging tips? Is there a strategic point in the code where I can proclaim (debug 3) and get the whole of mcclim compiled with debug info...? - -- +--------------------------------------------------------+ |Cyborg Animation Programmer | johnc@yagc.ndo.co.uk| |http://badbyteblues.blogspot.com -----------------------| +--------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCc3ktiwrK5pscc0RAg07AJ4t+OIm3YAY0GzwOfRsZulTsOK71ACgxLEu btFeA7H6tCwSh5b+1H3kbNc= =+ZQj -----END PGP SIGNATURE-----
John Connors <johnc@yagc.ndo.co.uk> writes:
How do I maximise the debuggability of mcclim? I'm going back to my mcclim texture generator app, this time using the gtk backend, hoping to stress it a bit. I'm using sbcl-0.9.16. & SLIME
Does anyone have any debugging tips? Is there a strategic point in the code where I can proclaim (debug 3) and get the whole of mcclim compiled with debug info...?
This is general SBCL information, not McCLIM information, but so it goes: (declaim (optimize (debug 3) (compilation-speed 3))) in your .sbclrc or in the repl. DO NOT LEAVE OUT THE COMPILATION-SPEED for now: otherwise SBCL will create more debug inforation than you really wan't for something the size of McCLIM -- this will hopefully change sooon, but for the moment that's the way it goes. If you do the declaim in a file, it will affect that file after the point of declamation, but nothing else. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."
participants (2)
-
John Connors
-
Nikodemus Siivola