about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2023-02-11 11:15:54 +0530
committerGitHub <noreply@github.com>2023-02-11 11:15:54 +0530
commit0e8f0b03cd94d9611063daaa516af2ae3489c6b5 (patch)
tree1c4e1a348748109ceaa217c76412f8f631b302da /tests/rustdoc-js-std/parser-errors.js
parent0781d5dd8e7ee76dfa2e3d6f78386231d2465a7a (diff)
parente97203c3f893893611818997bbeb0116ded2605f (diff)
downloadrust-0e8f0b03cd94d9611063daaa516af2ae3489c6b5.tar.gz
rust-0e8f0b03cd94d9611063daaa516af2ae3489c6b5.zip
Rollup merge of #106001 - sdroege:glibc-skip-over-null-argv, r=ChrisDenton
Stop at the first `NULL` argument when iterating `argv`

Some C commandline parsers (e.g. GLib and Qt) are replacing already handled arguments in `argv` with `NULL` and move them to the end. That means that `argc` might be bigger than the actual number of non-`NULL` pointers in `argv` at this point.

To handle this we simply stop iterating at the first `NULL` argument.

`argv` is also guaranteed to be `NULL`-terminated so any non-`NULL` arguments after the first `NULL` can safely be ignored.

Fixes https://github.com/rust-lang/rust/issues/105999
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions