GNU bug report logs - #64613
Signalling byte ops should show up in backtraces

Previous Next

Full log

Message #11 received at 64613 <at> debbugs.gnu.org (full text, mbox):

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: 64613 <at> debbugs.gnu.org
Cc: Alan Mackenzie <acm <at> muc.de>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.