From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Re: How to debug "Specified time is not representable" Date: Tue, 4 Oct 2011 13:47:07 +0200 Message-ID: <2011-10-04T13-45-53@devnull.Karl-Voit.at> References: <2011-09-30T16-30-44@devnull.Karl-Voit.at> <81lit6rskb.fsf@gmail.com> <2011-10-03T13-48-08@devnull.Karl-Voit.at> <6E314470-6664-496F-B0A8-D92EBFF398BB@gmail.com> Reply-To: news1142@Karl-Voit.at Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:43570) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB3Vh-0003Fw-Ka for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:50:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RB3Vg-0005yO-FY for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:50:09 -0400 Received: from lo.gmane.org ([80.91.229.12]:33762) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB3Vg-0005xw-8A for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:50:08 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RB3Vf-00055r-Eh for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 13:50:07 +0200 Received: from mail.michael-prokop.at ([88.198.6.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Oct 2011 13:50:07 +0200 Received: from news1142 by mail.michael-prokop.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Oct 2011 13:50:07 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Carsten! * Carsten Dominik wrote: > > I have no general method. However, you can do this: > > 1. On the "Options" menu, switch "Enter debug on error" on. > 2. Run your agenda to hit the error. A buffer with the backtrace > pops open. > 3. Press > > e (current-buffer) RET > > to learn about the buffer where this happens > > 4. Press > > e pos RET > > to learn about the position of the offending time stamp. > > 5. Press `q' to leave the backtrace buffer, then switch to the buffer > you learned about and find the position you just learned about. > THis should be the bad timestamp. *This* is the method I was searching for. *Thank* you very much. Now I can see the actual time stamp that causes any problem. -- Karl Voit