17 drracket:debug
Adds support for profiling information.
Shows the GUI information shown about the profile.
Hides the GUI information shown about the profile.
Tracks profiling information.
Tracks profiling information.
Tracks test case coverage information.
Tracks test case coverage information.
Tracks test case coverage information.
Tracks test case coverage information.
Displays the error message represented by the string, adding
embellishments like those that appears in the DrRacket REPL,
specifically a clickable icon for the stack trace (if the srcloc location is not empty),
and a clickable icon for the source of the error (read & syntax errors show their source
locations and otherwise the first place in the stack trace is shown).
If stack is false, then the stack traces embedded in the exn argument (if any)
are used. Specifically, this function looks for a stacktrace via
errortrace-key in the continuation marks of exn and
continuation-mark-set->context.
If stack is not false, that stack is added to the stacks already in the exception.
This should be called in the same eventspace and on the same thread as the error.
This function implements an error-display-handler in terms
of another error-display-handler.
See also Racket’s
error-display-handler
parameter.
If the current-error-port is the definitions window in
DrRacket, this error handler inserts some debugging
annotations, calls oedh, and then highlights the
source location of the runtime error.
Hides the backtrace window.
Adds the profiling preferences panel.
The result function first adds debugging information to
its argument and then passes it to oc.
The result function first adds debugging information to
its argument and then passes it to oe.
The name of the
style% object (in editor:get-standard-style-name)
used to indicate a covered region of code.
The name of the
style% object (in editor:get-standard-style-name)
used to indicate a region of code that tests (or any code, really)
didn’t cover.
Builds a url that goes to the trac report system.
The query argument is used as the
url’s query field.
The icon used in the DrRacket REPL when an exception is
raised that includes blame information blaming a PLaneT
package. (Clicking the icon connects to the PLaneT bug
report form.)
This function opens a DrRacket to display
debug-info. Only the src the position
and the span fields of the srcloc are considered.
The
edition-pair is used to determine if a
warning message is shown when before opening the file.
If the
edition-pair is not
#f, it is compared
with the result of
get-edition-number
of the editor that is loaded to determine if the file has been
edited since the source location was recorded. If so, it
puts up a warning dialog message to that effect.
Shows the backtrace window you get when clicking on the bug in
DrRacket’s REPL.
The error-message argument is the text of the error,
dis1 and dis2 are the stacktrace information,
extracted from the
continuation mark in the exception record, using
errortrace-key and using
continuation-mark-set->context.
The editions1 and editions2 arguments indicate
the editions of any editors
that are open editing the files corresponding to the source locations.
The lists must have the same length as dis1 and dis2.
The defs argument should be non-#f if there are
possibly stacktrace frames that contain unsaved versions of the
definitions window from DrRacket. Similarly, the ints argument
should be non-#f if there are possibly stacktrace frames that contain
unsaved versions of the interactions window.
Returns the background color used to highlight errors in the definitions window
(and other places, possibly).
The result depends on the 'framework:white-on-black? preference
setting.
Shows the backtrace window you get when clicking on the bug in
DrRacket’s REPL.
If dis is a list of srcloc?, then this function simply
calls drracket:debug:show-backtrace-window/edition-pairs,
passing error-message, dis, and a list of #f
that is as long as dis.
If dis is an exn:fail?, then this function calls
drracket:debug:show-backtrace-window/edition-pairs/two, extracting
the builtin stack trace (via continuation-mark-set->context)
and an errortrace stack trace from
the continuation marks in exn.