Some debug help

This is a moderated forum that collects tutorials, guides, and references for creating Transcendence extensions and scripts.
User avatar
Periculi
Fleet Officer
Fleet Officer
Posts: 1259
Joined: Sat Oct 13, 2007 7:48 pm
Location: By the beach

Post by Periculi » Sat Aug 30, 2008 7:01 pm

dbgLog crashes on me when I try (dbgLog (sysGlobals))

I wanted to take a look at the globals, and there is (sysGlobals) which outputs them, when used in dbgConsole it runs off the console, so I thought to try outputting the list to dbgLog- and get only crashing. :(

Then I tried filtering the list a little, but no luck.

User avatar
Betelgeuse
Fleet Officer
Fleet Officer
Posts: 1920
Joined: Sun Mar 05, 2006 6:31 am

Post by Betelgeuse » Sat Aug 30, 2008 8:06 pm

I can confirm it is crashing
maybe enuming them and outputting the individual elements would help.
Crying is not a proper retort!

User avatar
Periculi
Fleet Officer
Fleet Officer
Posts: 1259
Joined: Sat Oct 13, 2007 7:48 pm
Location: By the beach

Post by Periculi » Sat Aug 30, 2008 8:09 pm

I tried just getting the first 20 on the list returned and it still crashed with dbgLog. Maybe I can get them to output to console in chunks that don't go off the console panel.

User avatar
Betelgeuse
Fleet Officer
Fleet Officer
Posts: 1920
Joined: Sun Mar 05, 2006 6:31 am

Post by Betelgeuse » Sat Aug 30, 2008 8:11 pm

I don't know if it will help but this is the list that I used to make the function help list.

Code: Select all

			(setq functionLog (lambda nil
			
				(block nil
					(enum (sysGlobals) i
						(block (symbol)
							(setq symbol (eval (link i)))
							(if (isfunction symbol)
								(block (helpText)
									(setq helpText (fncHelp symbol))
									(if helpText
										(dbgLog helpText)
										(dbgLog "(" i " ...)")
										)
									)
								)
							)
						)
				
					(dbgOutput "Success")
					""
											
				)
			))
Crying is not a proper retort!

User avatar
Betelgeuse
Fleet Officer
Fleet Officer
Posts: 1920
Joined: Sun Mar 05, 2006 6:31 am

Post by Betelgeuse » Sun Aug 31, 2008 2:01 am

I found that dbgLog crashes if you have a string longer than 1003 characters
Crying is not a proper retort!

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests