Project

Profile

Help

Bug #5429

closed

when using no argument with new SaxonProcessor(), further code gives access violation

Added by Martin Honnen over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
C++ API
Start date:
2022-03-28
Due date:
% Done:

100%

Estimated time:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Found in version:
11.2
Fixed in version:
11.4
SaxonC Languages:
SaxonC Platforms:
SaxonC Architecture:

Description

Following up on https://saxonica.plan.io/boards/4/topics/8665 where I thought my trouble to get Saxon C HE 11.2 inside of a Notepad++ plugin were related to the environment I used it in I wrote a console app to see whether perhaps the proble exists there as well, and indeed, for me, on Windows at least, a simple console application using no argument to the SaxonProcessor constructor (https://www.saxonica.com/saxon-c/doc11/html/classSaxonProcessor.html#a5e96005ddffc24afef80bdc5714cb544)

crashes with

Exception thrown at 0x0000000000452014 (libsaxonhec.dll) in SaxonCArgumentLessConstructorTest.exe: 0xC0000005: Access violation reading location 0x0000000000000067.

#include

#include "SaxonProcessor.h"

#include <iostream>

#include "SaxonProcessor.h"


int main()
{
    std::cout << "Hello World!\n";

    SaxonProcessor* saxonProc = new SaxonProcessor();

    const char* version = saxonProc->version();

    std::cout << version << "\n";

    saxonProc->release();

    delete saxonProc;
}

Isn't that argument constructor meant to simply call new SaxonProcessor(false)?

Please register to edit this issue

Also available in: Atom PDF