"GET-VECTOR-SUBTYPE"
"HALT"
"IF-EQ" "INLINE-SYNTACTIC-CLOSURE-LAMBDA"
+ "INSERT-STEP-CONDITIONS"
"INSTANCE-REF" "INSTANCE-SET"
"IR2-COMPONENT-CONSTANTS" "IR2-CONVERT"
"IR2-PHYSENV-NUMBER-STACK-P"
"*ED-FUNCTIONS*"
"*MODULE-PROVIDER-FUNCTIONS*"
"WITH-TIMEOUT" "TIMEOUT"
+
+ ;; stepping interface
+ "STEP-CONDITION" "STEP-FORM-CONDITION"
+ "STEP-VALUES-CONDITION" "STEP-VARIABLE-CONDITION"
+ "STEP-CONDITION-FORM" "STEP-CONDITION-SOURCE-PATH"
+ "STEP-CONDITION-PATHNAME" "STEP-CONDITION-RESULT"
+ "STEP-CONTINUE" "STEP-NEXT" "STEP-INTO"
+ "*STEPPER-HOOK*"
;; RUN-PROGRAM is not only useful for users, but also
;; useful to implement parts of SBCL itself, so we're
;; INFO stuff doesn't belong in a user-visible package, we
;; should be able to change it without apology.
"*INFO-ENVIRONMENT*"
+
+ ;; stepping control
+ "*STEPPING*" "*STEP*"
"CLEAR-INFO"
"COMPACT-INFO-ENVIRONMENT"
"DEFINE-INFO-CLASS" "DEFINE-INFO-TYPE"
"FORMAT-ARGS-MISMATCH" "FORMAT-TOO-FEW-ARGS-WARNING"
"FORMAT-TOO-MANY-ARGS-WARNING" "EXTENSION-FAILURE"
+ "NAME-CONFLICT" "NAME-CONFLICT-FUNCTION"
+ "NAME-CONFLICT-DATUM" "NAME-CONFLICT-SYMBOLS"
+ "RESOLVE-CONFLICT"
+
;; ..and DEFTYPEs..
"INDEX" "LOAD/STORE-INDEX"
"SIGNED-BYTE-WITH-A-BITE-OUT"