"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"
"MORE-ARG-CONTEXT" "MOVABLE" "MOVE" "MULTIPLE-CALL"
"MULTIPLE-CALL-LOCAL" "MULTIPLE-CALL-NAMED"
"MULTIPLE-CALL-VARIABLE"
- "%%NIP-VALUES"
+ "%%NIP-DX" "%%NIP-VALUES"
"NLX-ENTRY" "NLX-ENTRY-MULTIPLE"
+ "NODE-STACK-ALLOCATE-P"
"NON-DESCRIPTOR-STACK" "NOTE-ENVIRONMENT-START"
"NOTE-THIS-LOCATION" "OPTIMIZER" "PACK-TRACE-TABLE"
"PARSE-EVAL-WHEN-SITUATIONS"
- "POLICY" "PREDICATE" "PRIMITIVE-TYPE" "PRIMITIVE-TYPE-OF"
+ "POLICY"
+ "%%POP-DX"
+ "PREDICATE" "PRIMITIVE-TYPE" "PRIMITIVE-TYPE-OF"
"PRIMITIVE-TYPE-OR-LOSE" "PRIMITIVE-TYPE-VOP"
"PRIMITIVE-TYPE-NAME" "PUSH-VALUES"
"READ-PACKED-BIT-VECTOR" "READ-VAR-INTEGER" "READ-VAR-STRING"
"*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"