Skip to content
Snippets Groups Projects
Select Git revision
  • dualcore
  • ch3/leds
  • wip-bootstrap default
  • ch3/time
  • master
5 results

tests

  • Clone with SSH
  • Clone with HTTPS
    • user avatar
    py/vstr: Raise a RuntimeError if fixed vstr buffer overflows.
    Damien George authored 
    Current users of fixed vstr buffers (building file paths) assume that there
is no overflow and do not check for overflow after building the vstr.  This
has the potential to lead to NULL pointer dereferences
(when vstr_null_terminated_str returns NULL because it can't allocate RAM
for the terminating byte) and stat'ing and loading invalid path names (due
to the path being truncated).  The safest and simplest thing to do in these
cases is just raise an exception if a write goes beyond the end of a fixed
vstr buffer, which is what this patch does.  It also simplifies the vstr
code.
    ede8a023
    History
    user avatar ede8a023
    History
    Name Last commit Last update
    ..
    basics
    bench
    cmdline
    cpydiff
    extmod
    feature_check
    float
    import
    inlineasm
    io
    jni
    micropython
    misc
    net_hosted
    net_inet
    pyb
    pybnative
    stress
    thread
    unicode
    unix
    wipy
    README
    pyboard.py
    run-bench-tests
    run-tests
    run-tests-exp.py
    run-tests-exp.sh
    README
    This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests" script in this directory.

Tests of capabilities not supported on all platforms should be written
to check for the capability being present. If it is not, the test
should merely output 'SKIP' followed by the line terminator, and call
sys.exit() to raise SystemExit, instead of attempting to test the
missing capability. The testing framework (run-tests in this
directory, test_main.c in qemu_arm) recognizes this as a skipped test.

There are a few features for which this mechanism cannot be used to
condition a test. The run-tests script uses small scripts in the
feature_check directory to check whether each such feature is present,
and skips the relevant tests if not.

When creating new tests, anything that relies on float support should go in the
float/ subdirectory.  Anything that relies on import x, where x is not a built-in
module, should go in the import/ subdirectory.