From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: Strange bug, request for more info Date: Thu, 31 Jan 2008 12:03:10 +0000 Message-ID: <20080131120310.GD21734@atlantic.linksys.moosehall> References: <20080131103218.GB21734@atlantic.linksys.moosehall> <8616E01A-5786-49E5-BA14-C5968EA2FE4A@science.uva.nl> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKY8Q-0002Es-95 for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 07:03:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKY8P-0002Dy-Is for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 07:03:13 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKY8P-0002DW-9E for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 07:03:13 -0500 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JKY8O-0004eM-Sq for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 07:03:13 -0500 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id m0VC3BqF002890 for ; Thu, 31 Jan 2008 06:03:11 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id m0VC3BCa002885 for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 12:03:11 GMT Content-Disposition: inline In-Reply-To: <8616E01A-5786-49E5-BA14-C5968EA2FE4A@science.uva.nl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On Thu, Jan 31, 2008 at 12:25:45PM +0100, Carsten Dominik wrote: > On Jan 31, 2008, at 11:32 AM, Adam Spiers wrote: > >I haven't seen it, but could you perhaps make use of edebug > >(conditional) breakpoints to track it down, or edebug evaluation > >lists, or even `edebug-set-global-break-condition' ? > > Hi Adam, > > yes, if I could *reproduce* this bug, I would use these tool to fix it. > But no-one, not even John can reliably reproduce it! Sure - that's why I was thinking that maybe you could come up with one or more conditional breakpoints which would be likely to trigger only when the bug occurs. In this way a conditional breakpoint would be a bit like the traditional "assertions" that people litter their code with as sanity checks, never expecting the checks to fail, but benefitting from the red flag if they do. For example in this case, presumably something's going wrong here: (defun org-agenda-goto (&optional highlight) "Go to the Org-mode file which contains the item at point." (interactive) (let* ((marker (or (get-text-property (point) 'org-marker) (org-agenda-error))) (buffer (marker-buffer marker)) (pos (marker-position marker))) (switch-to-buffer-other-window buffer) and similarly for `org-agenda-switch-to', in which case perhaps you could place conditional breakpoints asserting that the `buffer' and `pos' variable always end up with sane values?