From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Strange bug, request for more info Date: Thu, 31 Jan 2008 15:09:53 +0100 Message-ID: References: <20080131103218.GB21734@atlantic.linksys.moosehall> <8616E01A-5786-49E5-BA14-C5968EA2FE4A@science.uva.nl> <20080131120310.GD21734@atlantic.linksys.moosehall> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKa78-0006TX-Gt for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 09:10:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKa75-0006SL-MC for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 09:10:02 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKa75-0006SI-Ht for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 09:09:59 -0500 Received: from ug-out-1314.google.com ([66.249.92.173]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKa75-0001KP-9G for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 09:09:59 -0500 Received: by ug-out-1314.google.com with SMTP id a2so797994ugf.48 for ; Thu, 31 Jan 2008 06:09:58 -0800 (PST) In-Reply-To: <20080131120310.GD21734@atlantic.linksys.moosehall> 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: Adam Spiers Cc: emacs-orgmode@gnu.org On Jan 31, 2008, at 1:03 PM, Adam Spiers wrote: > 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? Hmmm, yes, i see now what you mean. I'll think about it. - Carsten