unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jason S. Cornez" <jcornez@ravenpack.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 6585@debbugs.gnu.org
Subject: bug#6585: 23.1; Hang / CPU 100% on background interaction when in minibuffer
Date: Fri, 16 Jul 2010 10:39:47 +0200	[thread overview]
Message-ID: <4C401AD3.7010005@ravenpack.com> (raw)
In-Reply-To: <4C4017DB.3080602@gmx.at>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/16/2010 10:27 AM, martin rudalics wrote:
>>   emacsclient -e '(my::switch-to-buffer "buffer")'
>>
>> That's almost certainly not exactly correct and I haven't tried it, but
>> it's the basic idea.
> 
> It's still a mystery to me why this should happen only when you
> byte-compile my::switch-to-buffer.
> 
> martin

I apologize, that is an assumption which I didn't test.  I do know that
when I edebug the function (C-u C-M-x) then I can use C-g.  And I could
see gdb that emacs was stuck in bytecode.c.  So I made the leap to byte
compiled being part of the problem.

Sorry for jumping to that conclusion.  In truth I don't know if
byte-compiling the function matters or not.

And I still haven't had a chance to work on a stand-alone test case.
Given that my own specific problem is resolved, I've mostly moved on.
But if I find the time to help some more, I'll post what I find.  Even
if that is just to say that I can't isolate the problem.

- -Jason
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxAGtMACgkQQlm6HDTMLyNZRgCfaV62a7Hk+W3ROFXVFoRqSaah
rZoAnRPf251n9B+Bbfh6Aa0MuE2YuHyD
=g5Yn
-----END PGP SIGNATURE-----





  reply	other threads:[~2010-07-16  8:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 14:19 bug#6585: 23.1; Hang / CPU 100% on background interaction when in minibuffer Jason Cornez
2010-07-08 16:52 ` Eli Zaretskii
2010-07-09  7:06 ` Jason S. Cornez
2010-07-14 10:27 ` Jason S. Cornez
     [not found] ` <handler.6585.B.12786062373280.ack@debbugs.gnu.org>
2010-07-15 12:05   ` Jason S. Cornez
2010-07-15 14:57     ` martin rudalics
2010-07-15 15:33       ` Jason S. Cornez
2010-07-16  8:27         ` martin rudalics
2010-07-16  8:39           ` Jason S. Cornez [this message]
2010-07-15 15:53     ` Johan Bockgård
2010-07-15 15:59       ` Jason S. Cornez
2010-08-31  6:42 ` Jason S. Cornez
2010-08-31 10:24   ` Stefan Monnier
2010-08-31 10:34     ` Jason S. Cornez
2010-08-31 13:09       ` Stefan Monnier
2010-08-31 15:09         ` Jason S. Cornez
2012-04-10 19:37           ` Stefan Monnier
2010-09-13 13:22 ` bug#6585: Patch welcome? Jason S. Cornez
2010-09-13 15:55   ` Stefan Monnier
2011-11-21 22:54 ` bug#6585: status of patch? Tim Connors
2011-11-22 21:47   ` Stefan Monnier
2011-11-23  7:02     ` Jason S. Cornez

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C401AD3.7010005@ravenpack.com \
    --to=jcornez@ravenpack.com \
    --cc=6585@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.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).