From: Ihor Radchenko <yantar92@posteo.net>
To: Rens Oliemans <hallo@rensoliemans.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tips on reproducing and bisecting bugs
Date: Thu, 07 Sep 2023 11:44:24 +0000 [thread overview]
Message-ID: <87il8mnr6v.fsf@localhost> (raw)
In-Reply-To: <87v8cn3w9c.fsf@rensoliemans.nl>
Rens Oliemans <hallo@rensoliemans.nl> writes:
> Thanks for creating and maintaining Org mode, it's great. I tried helping out recently by
> confirming and bisecting a reported bug
> (https://list.orgmode.org/CAMJKaZz6sRDOxV6rhmdM97enhYsNTodtcTCZNn1ZbQUk3GH9Lw@mail.gmail.com/),
> but am not sure if what I did was actually useful, and if so, how to do this more
> efficiently.
Thanks!
Confirming bug reports is always helpful.
Bisecting is also helpful, but usually requires more work that is not
always necessary - some bugs may be fixed very quickly, quicker than
the time needed to complete git bisect, using Elisp debugging tools.
We usually use bisecting as the last resort, when it is not clear what
is causing a particularly mysterious bug.
> I have the orgmode repo cloned, and build orgmode with `make && make vanilla`. When
> bisecting, I manually navigate to and load the required init.el and reproduce the bug per
> commit. It seems that parameters passed to `make vanilla` are not passed to emacs. Is this
> how you would do it, or do you have tips to improve this workflow? Additionally, how could
> I do this for different emacs versions?
You can use "make repro" command that, in addition to creating a clean
Emacs environment, sets up some debugging tools. See
https://orgmode.org/manual/Feedback.html#Feedback
I usually reproduce things using
make repro REPRO_ARGS="-l /path/to/init.el /path/to/bug.org" EMACS=/path/to/specific/emacs/version
> If it wasn't all that useful, what can I do to improve this? I have a little bit of lisp
> knowledge, but no experience with the orgmode source code (yet).
You may also check out https://orgmode.org/worg/org-contribute.html
And feel free to ask questions, if something is not clear.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-09-07 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 20:02 Tips on reproducing and bisecting bugs Rens Oliemans
2023-09-07 11:44 ` Ihor Radchenko [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il8mnr6v.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=hallo@rensoliemans.nl \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).