From: Anand Tamariya <atamariya@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Java: Jump to file from stacktrace
Date: Mon, 19 Apr 2021 19:17:20 +0530 [thread overview]
Message-ID: <CADm7Y4n8MZschP1ALsJcVBeCHbOamXV=ErOxZ4c4YbXiEzG_Ng@mail.gmail.com> (raw)
In-Reply-To: <8335vmtpio.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
> Thanks, but could you please describe the scenario where this feature
> would be useful? I'm not sure I understand that, especially what kind
> of "log" is supposed to include a stacktrace, and what do GUD and EDE
> have to do with this?
>
Java applications typically log execution steps in a log file. This
includes exceptions as well (a sample
<https://preview.redd.it/74g3ys4g4yt61.png?width=939&format=png&auto=webp&s=c976e31ffd54d1087fa13211dc39ed3fadc4c66a>).
The log files are usually collected after reproducing the error scenario
and analyzed. So these can be large. next-error command can take one
straight to the stacktrace location. Using the file and line number, one
can figure out possible causes of errors. If one could click on it and
reach the destination, it's even better.
I'm using this for jumping into code while running debug sessions with GUD.
EDE just has a handy API for finding file by name. That's why I used that
as an example.
[-- Attachment #2: Type: text/html, Size: 1272 bytes --]
prev parent reply other threads:[~2021-04-19 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 14:51 Java: Jump to file from stacktrace Anand Tamariya
2021-04-19 6:15 ` Anand Tamariya
2021-04-19 12:41 ` Eli Zaretskii
2021-04-19 13:47 ` Anand Tamariya [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='CADm7Y4n8MZschP1ALsJcVBeCHbOamXV=ErOxZ4c4YbXiEzG_Ng@mail.gmail.com' \
--to=atamariya@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.