From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: How to debug "Specified time is not representable" Date: Tue, 4 Oct 2011 13:41:14 +0200 Message-ID: <6E314470-6664-496F-B0A8-D92EBFF398BB@gmail.com> References: <2011-09-30T16-30-44@devnull.Karl-Voit.at> <81lit6rskb.fsf@gmail.com> <2011-10-03T13-48-08@devnull.Karl-Voit.at> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:59530) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB3NC-0000go-TL for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:41:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RB3N6-0004T6-Uw for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:41:22 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:40008) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB3N6-0004Sz-Qb for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 07:41:16 -0400 Received: by wwp14 with SMTP id 14so462479wwp.30 for ; Tue, 04 Oct 2011 04:41:16 -0700 (PDT) In-Reply-To: <2011-10-03T13-48-08@devnull.Karl-Voit.at> 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: news1142@Karl-Voit.at Cc: emacs-orgmode@gnu.org On Oct 3, 2011, at 1:50 PM, Karl Voit wrote: > Hi! >=20 > * Jambunathan K wrote: >> Karl Voit writes: >>=20 >>> When I get =ABSpecified time is not representable=BB while creating = the >>> Agenda view, I want to get more information *where* the problem is. >>>=20 >>> I found [1] and following and so I got it that there is no way of >>> managing timestamps before 1970 :-( >>>=20 >>> Is there a way to get to the problematic time stamp? >>> 1. = http://lists.gnu.org/archive/html/emacs-orgmode/2011-05/msg00729.html >>=20 >> Hope you have looked at C-h v org-read-date-force-compatible-dates=20 >=20 > Meanwhile: yes. >=20 > I do not want to use timestamps outside of UNIX epoch. I just wanted > to *locate* the culprit. >=20 >> A simple M-x grep-find on .org files for the year should work. >=20 > I do not know the year. >=20 >> You may also try >> M-x debug-on-entry RET ding RET >> Look at the backtrace and see whether you can get some clues. >=20 > Sorry, no clue. 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=20 e (current-buffer) RET to learn about the buffer where this happens 4. Press =20 e pos RET to learn about the position of the offending time stamp. =20 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. HTH - Carsten >=20 >> Works best if your orgmode is not compiled >=20 > When I have compiled Orgmode, should I delete all *.elc files? >=20 > --=20 > Karl Voit >=20 >=20 - Carsten