From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Jorge Solórzano <jorsol(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14584: Segmentation fault importing large XML file |
Date: | 2017-03-08 19:54:37 |
Message-ID: | 13153.1489002877@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2017-03-08 20:17 GMT+01:00 Jorge Solórzano <jorsol(at)gmail(dot)com>:
>> I installed debug symbols for libxml2 if this helps:
>> #0 xmlParserPrintFileContextInternal (input=input(at)entry=0x55afc89ef4b0,
>> channel=0x55afc636ca30 <appendStringInfo>, data=0x55afc89e5cc0) at
>> ../../error.c:181
> It looks not well handled libxml2 fatal error "internal error: Huge input
> lookup"
Yeah. The segfault is inside xmlParserPrintFileContext(), so really there
is at least one libxml2 bug here and possibly two. Maybe it should have
been able to cope with such large input, or maybe not, but for sure its
printing functions should have been able to cope with the state at the
time the error was reported.
I don't think there's much we can do about it; you need to report this
to the libxml2 folk.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Solórzano | 2017-03-08 20:02:06 | Re: BUG #14584: Segmentation fault importing large XML file |
Previous Message | Pavel Stehule | 2017-03-08 19:36:08 | Re: BUG #14584: Segmentation fault importing large XML file |