cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
13 lines
1000 B
OpenEdge ABL
13 lines
1000 B
OpenEdge ABL
%feature("docstring",
|
|
"A container for options to use when creating watchpoints."
|
|
) lldb::SBWatchpointOptions;
|
|
|
|
%feature("docstring", "Sets whether the watchpoint should stop on read accesses."
|
|
) lldb::SBWatchpointOptions::SetWatchpointTypeRead;
|
|
%feature("docstring", "Gets whether the watchpoint should stop on read accesses."
|
|
) lldb::SBWatchpointOptions::GetWatchpointTypeRead;
|
|
%feature("docstring", "Sets whether the watchpoint should stop on write accesses. eWatchpointWriteTypeOnModify is the most commonly useful mode, where lldb will stop when the watched value has changed. eWatchpointWriteTypeAlways will stop on any write to the watched region, even if it's the value is the same."
|
|
) lldb::SBWatchpointOptions::SetWatchpointTypeWrite;
|
|
%feature("docstring", "Gets whether the watchpoint should stop on write accesses, returning WatchpointWriteType to indicate the type of write watching that is enabled, or eWatchpointWriteTypeDisabled."
|
|
) lldb::SBWatchpointOptions::GetWatchpointTypeWrite;
|