asterisk followed immediately by a newline causes crash #323

Closed
g2flyer opened this Issue Dec 6, 2012 · 9 comments

Projects

None yet

3 participants

@g2flyer
g2flyer commented Dec 6, 2012

Since the big update i get "Error: null" errors during the synchronization. It seems a few files trigger a (null pointer?) bug somewhere and stop synchronization. If i repeat hitting the synchronization button often enough, it will eventually go through all files and finish. However, files for which i got the null error show up as empty (others seem ok). These files in emacs though all show properly in org-mode 7.9.2 and i couldn't find any pattern which distinguishes them from files which do not cause the problem. Lastly, i sync from the sdcard and run on android 2.3.7 (cyanogenmod7.2) ...

@matburt
Owner
matburt commented Dec 7, 2012

duplicate of issue #322

@matburt matburt closed this Dec 7, 2012
@matburt
Owner
matburt commented Dec 7, 2012

@g2flyer check out the responses on issue #322.

On Thu, Dec 6, 2012 at 6:30 PM, g2flyer notifications@github.com wrote:

Since the big update i get "Error: null" errors during the
synchronization. It seems a few files trigger a (null pointer?) bug
somewhere and stop synchronization. If i repeat hitting the synchronization
button often enough, it will eventually go through all files and finish.
However, files for which i got the null error show up as empty (others seem
ok). These files in emacs though all show properly in org-mode 7.9.2 and i
couldn't find any pattern which distinguishes them from files which do not
cause the problem. Lastly, i sync from the sdcard and run on android 2.3.7
(cyanogenmod7.2) ...


Reply to this email directly or view it on GitHubhttps://github.com/matburt/mobileorg-android/issues/323.

@g2flyer
g2flyer commented Dec 7, 2012

Hmm, the no-space-after-asterix mentioned in #322 cannot be the problem i face: neither a manual/visual inspection nor a egrep '*[^ *]' on the files does not reveal anything along these lines!
But maybe it is something related: are there maybe other assumptions on what an asterix line is (not) allowed to contain, e.g., do you expect there is no quotes, paranthesis, links or alike in the text following the asterix?
I'll try to do a binary trial'n'error search on the files maybe i can find it out myself but any hints on how to best to debug it would be appreciated. thanks

@hdweiss hdweiss reopened this Dec 7, 2012
@hdweiss
Collaborator
hdweiss commented Dec 7, 2012

Perhaps having an asterisk followed immediately by a newline?

@g2flyer
g2flyer commented Dec 8, 2012

Henning, you are absolute correct: this was the problem. removing them makes the sync working smoothly ...

@g2flyer g2flyer closed this Dec 8, 2012
@hdweiss hdweiss reopened this Dec 8, 2012
@hdweiss
Collaborator
hdweiss commented Dec 8, 2012

@g2flyer ok, good that you found the bug. I'm gonna open this again, as mobileorg shouldn't crash in this case.

@hdweiss
Collaborator
hdweiss commented Dec 11, 2012

@g2flyer I'm unable to reproduce this crash. Can you provide a minimal file that causes the crash?

@hdweiss hdweiss was assigned Dec 11, 2012
@hdweiss hdweiss closed this Dec 13, 2012
@g2flyer
g2flyer commented Dec 13, 2012

Henning, sorry for replying to your question only now: I can in fact still reproduce my problem, e.g., with a file containing nothing else but a single * and a newline. However, this test is based on the latest version in the Android market, not from the source. So maybe the bug fix is already and but just not yet published? In any case, the places i had the * were rather silly (conversion from legacy files where ****************** underlined some heading) and these * didn't really make any sense in org-files, so finding them due to this bug and cleaning them up was actually a good thing :-)

@hdweiss
Collaborator
hdweiss commented Dec 14, 2012

Alright, perhaps it is fixed already. Feel free to re-open this issue if you keep experiencing the same problem with the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment