On Thu, 2012-03-01 at 21:08 +0200, Juha Pahkala wrote:
> On 03/01/2012 04:25 PM, Patrick Ohly wrote:
> >> Hmm, don't know gdb at all, but I do have some experience of debugging
> >> and stepping through source code... so I'm pretty sure I'll be able to 
> >> help.
> >
> > Please give it a try.[snip]
> 
> Thanks for the detailed instructions, I *think* I got it right. Here's 
> what I did:
> 
> gdb /usr/libexec/syncevo-dbus-server
> (gdb) run
[...]
> #1  0x00d897ea in xmlHTMLEntity (pScanner=<optimized out>, 
> begin=0xbfffe288,
>      len=0xbfffe28c)
>      at 
> /home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:667

Bingo.

Some of the vCards contain characters which were encoded using numeric
character references, for example @ became &#64; - these entities are
not handled by xmlHTMLEntity().

Of course, when I fed your message into the parser here I had picked
only the first contact, which didn't have an email address and thus
didn't trigger the problem.

I am unsure whether numeric character references are valid in XML. They
are certainly not necessary for things like the at sign, which has no
special meaning in XML.

I should be able to reproduce and fix the problem now. Stay tuned...

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to