all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: schwab@linux-m68k.org, michael_heerdegen@web.de
Cc: 24764@debbugs.gnu.org
Subject: bug#24764: 25.1.50; Another crash in automatic gc
Date: Sat, 22 Oct 2016 15:36:37 +0300	[thread overview]
Message-ID: <837f90r25m.fsf@gnu.org> (raw)
In-Reply-To: <83a8dwr3sa.fsf@gnu.org> (message from Eli Zaretskii on Sat, 22 Oct 2016 15:01:25 +0300)

> Date: Sat, 22 Oct 2016 15:01:25 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: michael_heerdegen@web.de, 24764@debbugs.gnu.org
> 
> > Finding the place where a member of a struct buffer is overwritten
> > can be done with a watchpoint.
> 
> Yes.  But IME just a watchpoint with no conditions gets triggered too
> frequently to be useful

For example, in this case, we are talking about the buffer->markers
member, which is changed (a.k.a. "overwritten") each time a new marker
is added to the buffer, because a new marker 'm' is added to its
buffer 'b' as follows:

      m->next = BUF_MARKERS (b);
      BUF_MARKERS (b) = m;

So setting a watchpoint on b->markers needs to know (1) the buffer in
which this happens, (2) the value or range of values that the
'markers' pointer is overwritten with, in order to make the watchpoint
conditional.





  parent reply	other threads:[~2016-10-22 12:36 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22  9:38 bug#24764: 25.1.50; Another crash in automatic gc Michael Heerdegen
2016-10-22 10:05 ` Eli Zaretskii
2016-10-22 11:41   ` Andreas Schwab
2016-10-22 12:01     ` Eli Zaretskii
2016-10-22 12:21       ` Eli Zaretskii
2016-10-22 14:05         ` Michael Heerdegen
2016-10-22 14:10           ` Eli Zaretskii
2016-10-22 14:43             ` Michael Heerdegen
2016-10-22 15:08               ` Eli Zaretskii
2016-10-22 18:25                 ` Michael Heerdegen
2016-10-22 18:35                   ` Eli Zaretskii
2016-10-23  9:06                     ` Michael Heerdegen
2016-10-23  9:32                       ` Eli Zaretskii
2016-10-23 10:22                         ` Eli Zaretskii
2016-10-23 10:53                           ` Michael Heerdegen
2016-10-23 12:06                             ` Eli Zaretskii
2016-10-23 10:49                         ` Michael Heerdegen
2016-10-23 10:24                       ` Eli Zaretskii
2016-10-23 11:00                         ` Michael Heerdegen
2016-10-23 12:08                           ` Eli Zaretskii
2016-10-23 13:57                           ` Eli Zaretskii
2016-10-23 15:53                             ` Michael Heerdegen
2016-10-23 16:37                               ` Michael Heerdegen
2016-10-23 17:01                                 ` Eli Zaretskii
2016-10-25 14:37                                   ` Michael Heerdegen
2016-10-25 16:46                                     ` Eli Zaretskii
2016-10-25 17:21                                       ` Michael Heerdegen
2016-10-25 18:17                                         ` Eli Zaretskii
2016-10-27 16:40                                         ` Michael Heerdegen
2016-10-27 17:18                                           ` Eli Zaretskii
2016-11-07  3:38                                           ` Eli Zaretskii
2016-11-07 11:36                                             ` Michael Heerdegen
2016-10-22 12:36       ` Eli Zaretskii [this message]
2016-10-22 13:54   ` Michael Heerdegen
2016-10-22 14:12     ` Michael Heerdegen
2016-10-22 14:24       ` Eli Zaretskii
2016-10-22 14:13     ` Eli Zaretskii
2016-10-23  9:32       ` Michael Heerdegen
2016-10-22 14:37 ` npostavs
2016-10-22 14:38   ` Eli Zaretskii
2016-10-22 14:51     ` Michael Heerdegen
2016-10-22 15:25       ` Eli Zaretskii
2016-10-22 15:33         ` Eli Zaretskii

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=837f90r25m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24764@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=schwab@linux-m68k.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.