[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Different behaviour while debugging?
From: |
Thorsten Jolitz |
Subject: |
Different behaviour while debugging? |
Date: |
Wed, 20 Feb 2013 15:57:01 +0100 |
User-agent: |
Gnus/5.130002 (Ma Gnus v0.2) Emacs/24.2 (gnu/linux) |
Hi List,
I have the very strange case that a program - in some special situation
- does not work as expected, but when I instrument the relevant
function(s) for edebug and single-step through them, everythings works
as expected and the output is fine.
There are no errors involved, so 'toggle-debug-on-error does not help.
Its just that the program should put a buffer temporarily into a given
major-mode and uncomment some comment-lines with 'uncomment-region' before
turning-on Org-mode.
With other modes it works fine, but in case of html-mode, this step is
simply omitted when running the program as-is, but is successfully
completed when single-stepping with edebug.
How can that be? Has elisp become just *too* fast for correct program
execution and programs work only reliably when slowed down by debugging?
To be more precise, inserting 'message functions in the relevant
program-function revealed that:
1. the function is entered
2. the buffer is in the expected (html) mode
but inside the 'cond function in the while loop, the out-commented lines
("comline") are not recognized when run normally
,--------------------------------------
| Entering outorg-convert-to-org....
| html-mode
| Entering while-loop ...
| Entering codeline after codeline ....
| Entering while-loop ... [2 times]
| Entering codeline after codeline ....
| Entering while-loop ...
| Entering codeline after codeline ....
| Entering while-loop ... [2 times]
| Entering codeline after codeline ....
`--------------------------------------
while they are recognized correctly when single-stepping with edebug
,-------------------------------------------
| Edebug: outorg-convert-to-org
|
| Entering outorg-convert-to-org....
| html-mode
| Entering while-loop ...
| Entering comline after comline or bobp ...
| Entering while-loop ...
| Entering comline after comline or bobp ...
| Entering while-loop ...
| Entering comline after comline or bobp ...
| Entering while-loop ...
| Entering codeline after comline ....
`-------------------------------------------
Strange, isn't it?
--
cheers,
Thorsten
Re: Different behaviour while debugging?, Andreas Röhler, 2013/02/22