From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Ok, somebody give me a clue.
Date: Mon, 28 Feb 2005 15:06:04 +0100 [thread overview]
Message-ID: <m37jks93ub.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <x54qfwki43.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 28 Feb 2005 13:02:20 +0100")
David Kastrup <dak@gnu.org> writes:
> For debugging purposes, I have been using the following:
>
> struct trbuf { void* pc; int value; } trbuf[256];
> unsigned char trptr;
> #define RECORD_INPUT do { __label__ woozle; \
> woozle: trbuf[trptr++] = (struct trbuf) \
Does [trptr++%256] give better results ?
> { &&woozle, interrupt_input_blocked}; } while(0)
>
> And then whereever I change interrupt_input_blocked, I also call
> RECORD_INPUT. This causes Emacs to crash in unrelated spaces. I have
> crosschecked the compiled code, and it does the correct thing: no data
> type overflow problems or something.
>
> So it is obvious that the problem is elsewhere, likely that the data
> structures I use above confuse the garbage collector. What kind of
> data structures are allowed, and how can I hide data structures that
> would confuse it from the garbarge collector?
>
> --
> David Kastrup, Kriemhildstr. 15, 44793 Bochum
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>
>
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-02-28 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 12:02 Ok, somebody give me a clue David Kastrup
2005-02-28 14:06 ` Kim F. Storm [this message]
2005-02-28 14:48 ` Andreas Schwab
2005-02-28 16:20 ` David Kastrup
2005-02-28 15:55 ` David Kastrup
2005-03-02 11:23 ` Richard Stallman
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=m37jks93ub.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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 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).