Michael Gilbert michael.s.gilb...@gmail.com writes:
poppler.
Ah indeed they have a slightly modified version:
inline static void *gmallocn(int nObjs, int objSize, bool checkoverflow)
{
int n;
if (nObjs == 0) {
return NULL;
}
n = nObjs * objSize;
if (objSize = 0 || nObjs 0 ||
retitle 504489 user-specific crash with fullcircle pdf file
severity 504489 minor
tag 504489 moreinfo, unreproducible
thanks
Timo Juhani Lindfors wrote:
I still see the error message in 3.03-4
$ xpdf fullcircle-issue18eng.pdf 19
Bogus memory allocation size
I do get the Bogus memory
Michael Gilbert michael.s.gilb...@gmail.com writes:
I do get the Bogus memory allocation size message, but I just don't
get a crash afterward (tested on amd64 and i386). Can you capture a
backtrace? Also, can you send updated system information for your
machine (easiest to generate with
Timo Juhani Lindfors wrote:
Michael Gilbert michael.s.gilb...@gmail.com writes:
I do get the Bogus memory allocation size message, but I just don't
get a crash afterward (tested on amd64 and i386). Can you capture a
backtrace? Also, can you send updated system information for your
Michael Gilbert michael.s.gilb...@gmail.com writes:
Is there any reason to keep this bug open just for an innocuous
message?
Not sure but hmm, what makes you think this is innocuous? Now that I
grep the code I find only two fragments that mention it but both have
exit(1) after them:
void
Timo Juhani Lindfors wrote:
Michael Gilbert michael.s.gilb...@gmail.com writes:
Is there any reason to keep this bug open just for an innocuous
message?
Not sure but hmm, what makes you think this is innocuous? Now that I
grep the code I find only two fragments that mention it but both
Package: xpdf-reader
Version: 3.02-1.3
Severity: normal
Steps to reproduce:
1) wget http://iki.fi/lindi/fullcircle-issue18eng.pdf
2) xpdf fullcircle-issue18eng.pdf 19
Expected results:
2) xpdf shows page 19 of the full circle magazine
Actual results:
2) xpdf exits and prints Bogus memory
7 matches
Mail list logo
