I need help - I can help - Access Violations on New Page

Print Page | Close Window

Access Violations on New Page

Printed From: Debenu Quick PDF Library - PDF SDK Community Forum
Category: For Users of the Library
Forum Name: I need help - I can help
Forum Description: Problems and solutions while programming with the Debenu Quick PDF Library and Debenu PDF Viewer SDK
URL: http://www.quickpdf.org/forum/forum_posts.asp?TID=526
Printed Date: 19 May 24 at 6:10AM
Software Version: Web Wiz Forums 11.01 - http://www.webwizforums.com

Topic: Access Violations on New Page

Posted By: Freebopper
Subject: Access Violations on New Page
Date Posted: 03 Oct 06 at 2:10AM

Hi All..

We have been using the library without problem for a year or so. Recently we made some report mods and now we are getting AV's which appear to be generated by the library.
Tracking it down it occurs in uPDFPageTree at line 621 in our version, which is V5.11.

function TPDFPageTree.ResourcesDict: TPDFDictionary;
var
Obj: TPDFObject;
begin
Obj := FPageDict.FindValueByKeyName('Resources');

"FPageDict" is not assigned. It doesn't always happen, seeming to depend upon what gui activity there's been in the app.

Has anyone had any experience of this?
I do hope so!

Regards,

Don

-------------
Don

Replies:

Posted By: marian_pascalau
Date Posted: 26 Oct 06 at 7:29AM

Don, I had once a similar problem. The problem was that I did not checked the return code while loading my PDF document. The document was not loaded, I ignored that error and I run into troubles.

You should check your sourcecode for each returned exit code. If everithing was ok, please send me your pdf document and I will officialy log your problem into our bug list.

My email: marian_pascalau(at)hotmail.com

Regards, Marian

Posted By: Freebopper
Date Posted: 26 Oct 06 at 7:52PM

Thanks for your reply, Marian.

However, and I should have already posted this, the fault was not with the library but with our code: we were writing beyond the end of a dynamic array, and it just so happened that the memory we trampled was being used by the NewPage routine.

So, to our great relief, no bug in the library.

-------------
Don