CFDump and the standard Coldfusion Debugging Error Information didn't work. Charlie Arehart has mentioned several reasons why use a debugger when you can just use CFDump. I ran across a specific CFDUMP instance today when I found this very true. I was passing an xml string into a SQL Stored Procedure. The xml string was being set using cfsavecontent.



I would get an error saying something like xml error in sql, page tag not closed when running the page, so looking @ the xml string with CFDump everything looked fine. I knew some reason the xml was getting truncated during the call but didn't know why.



I copied the query from the sql presented in the CF error message in the CFDUMP and tried it in my SQL editor and it worked fine. I also copied the xml dump and pasted in the proc and it worked. So what is the problem, why was the xml was being truncated?

Myth: All I need is CFDump is rated Busted

Snapshot of my Expressions view:

Notice the tabs, breaks, and returns were being saved within the xml string. When I copied the variable output from the Expression view in the left area to my SQL editor, I got the sql error. Finally, so I knew why I was getting the error and fixed it by removed all tabs, etc in my cfm page and the page worked fine.

MythBusters: All I need is CFDump