[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64613: Signalling byte ops should show up in backtraces
|
From: |
Mattias Engdegård |
|
Subject: |
bug#64613: Signalling byte ops should show up in backtraces |
|
Date: |
Wed, 26 Jul 2023 19:07:27 +0200 |
Now (82f5f3b8a2) the `aref` and `aset` byte-ops provide backtrace records for
errors that are discovered in the fast path:
- index argument not a fixnum
- for vector and record arguments, index out of range
For other types there is no such help yet since we call out to Faref and Faset.
We need a general strategy for dealing with such call-outs from the bytecode
engine. So far, the backtrace records have all been to cold paths with no new
hot-path code.