From: Per Bothner <per@bothner.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>, kawa <kawa@sourceware.org>
Subject: Re: Spurious line numbers
Date: Mon, 18 Sep 2023 17:08:55 -0700 [thread overview]
Message-ID: <6366ab02-2a8f-ac67-dce8-6b7515c9a81b@bothner.com> (raw)
In-Reply-To: <CAMFYt2ZDHV+UmL2jW8Ygpfqh0khgs7kZjgAOqMh4V3sg5JhEMQ@mail.gmail.com>
On 9/18/23 14:25, Panicz Maciej Godek via Kawa wrote:
> I have a question.
> Recently, I've been developing a module called "stepper", and as I
> occasionally get some stack traces, they look more or less like this:
>
> at gnu.mapping.Procedure.apply2(Procedure.java:160)
> at stepper$frame7.lambda33reduce(stepper.scm:10145)
> at stepper$frame7.lambda33reduce(stepper.scm:10108)
> at stepper.reduce$check(stepper.scm:541)
I believe this is generated in this file: gnu/bytecode/SourceDebugExtAttr.java.
This was meant to handle the SourceDebugExtension from JSR-45,
and (reading from the commment) it's meant to provide a "fall-back" mode.
I *think* this may happen if you use (include ...) or possibly
if expanding a macro defined in a different file.
Probably if you subtract 10000 you might get a reasonable result.
I don't know how many current debuggers make use of SourceDebugExtension.
The hope is you would get a better stack trace if you use a
SourceDebugExtension-aware debugger, but perhaps we should stop generating it.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2023-09-19 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 21:25 Panicz Maciej Godek
2023-09-19 0:08 ` Per Bothner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6366ab02-2a8f-ac67-dce8-6b7515c9a81b@bothner.com \
--to=per@bothner.com \
--cc=godek.maciek@gmail.com \
--cc=kawa@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).