all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: akrl@sdf.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: Possible Race condition? Re: origin/features/native-comp: Where do jitted .eln files  go?
Date: Tue, 25 Aug 2020 13:19:51 -0700	[thread overview]
Message-ID: <24389.29287.103901.450906@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <xjf8se233k3.fsf@sdf.org>

Any tips on how to isolate / produce  a bug trace? Note that
--debug-init did not produce a backgtrace Andrea Corallo writes:
 > "T.V Raman" <raman@google.com> writes:
 > 
 > > Hi Andrea,
 > >
 > > In my emacs startup, I load dired-x. In my customization settings, I
 > > have dired-omit-mode in my dired-mode-hook.
 > >
 > > Works fine with plain emacs, but throws this error in *Messages*
 > > (starting with --debug-init does not produce a backtrace.
 > >
 > > Symbol’s function definition is void: dired-omit-mode
 > >
 > > Suspect some kind of race condition.
 > > f
 > 
 > Hi Raman,
 > 
 > I'd bet more on some other kind of bug.  If you could isolate it and
 > open a bug with a reproducer would be appretiated.
 > 
 > Thanks!
 > 
 >   Andrea
 >   
 > -- 
 > akrl@sdf.org

-- 
♉Id: kg:/m/0285kf1  🦮♉

--
♉Id: kg:/m/0285kf1  🦮♉



  reply	other threads:[~2020-08-25 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 19:52 origin/features/native-comp: Where do jitted .eln files go? T.V Raman
2020-08-25  6:18 ` Andrea Corallo via Emacs development discussions.
2020-08-25 15:23   ` Possible Race condition? " T.V Raman
2020-08-25 19:53     ` Andrea Corallo via Emacs development discussions.
2020-08-25 20:19       ` T.V Raman [this message]
2020-08-25 21:04         ` Andrea Corallo via Emacs development discussions.
     [not found]   ` <24394.59245.98750.79288@google.com>
     [not found]     ` <xjf8sdwzjov.fsf@sdf.org>
2020-08-30 14:07       ` T.V Raman
2020-08-30 20:33         ` Andrea Corallo via Emacs development discussions.

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=24389.29287.103901.450906@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=akrl@sdf.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.