From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: kawa <kawa@sourceware.org>
Subject: Spurious line numbers
Date: Mon, 18 Sep 2023 23:25:18 +0200 [thread overview]
Message-ID: <CAMFYt2ZDHV+UmL2jW8Ygpfqh0khgs7kZjgAOqMh4V3sg5JhEMQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
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)
The problem with the second and the third line is that the stepper module
contains some 700 lines, so that the lines 10145 and 10108 don't even exist.
What is the likely reason for this behavior?
(I can help reproduce it if needed - in the sources of GRASP - but I don't
think I'll find time to build a minimal reproducible example)
next reply other threads:[~2023-09-18 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 21:25 Panicz Maciej Godek [this message]
2023-09-19 0:08 ` Per Bothner
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=CAMFYt2ZDHV+UmL2jW8Ygpfqh0khgs7kZjgAOqMh4V3sg5JhEMQ@mail.gmail.com \
--to=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).