Break
Prev
Next

Break

Break at a template, at a location in a stylesheet or xml file loaded by xsldbg, or at the current node. New for xsldbg 3.1.4: When in gdb compatabilty mode orpaned breakpoints can be set at a specific file and line number and be resolved to an active later on.

Shortcut name: b

xsldbg will try to guess the complete URL given a

file name without a path specified.
a file name in the same directory as the "top" stylesheet loaded
a file name relative to the current working directory of xsldbg
Ie if you have loaded a stylesheet file of ../en/xsldoc.xsl you can do this

break -l xsldoc.xsl 26

This command will match a partial or complete QNAME template and or mode name provided. Eg "template" will ma/tch any QNAME with a local part of "template"

Any name spaces in the provided QNAME will be expanded as specified by the names spaces defined in the XSL SOURCE file. eg "xsl:test1" will be expanded to "http://www.w3.org/199/XSL/Transform:test1"

A requested breakpoint may need to be resolved to its associated URL and line number. This is done automaticly after the first template has been seen by xsldbg. Breakpoints are re-validated shortly after the start of each run.

Automatic breakpoint validation is used when gdb mode is enabled - the default behaviour of xsldbg

Table 3.4. Break usage

break -l <FILENAME> <LINENO>    (To set breakpoint at specified file, line number)
break -l <URI> <LINENO>    (To set breakpoint at specified URI, line number)
break <TEMPLATE_NAME>    (To break at named or matched template.)
break <TEMPLATE_NAME> <MODE_NAME>    (To break at named template with given mode.)>
break "" <MODE_NAME>    (To break at any template that has a given mode name)
break *    (To break at any template found.)
break \*    (To break at the "*" template. Other name that include '*' will not be treated specialy.)
break     (To break point at current node. Yes that includes xml data nodes!)
Prev
Next
Home


Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team