openjade 1.3.2, Revision 2: demo failure

[tom.duck@…]

Openjade has a demo program that can be used to test the installation. See ​http://olympus.het.brown.edu/cgi-bin/dwww?type=file&location=/usr/share/doc/openjade#using.

Execution of the demo results in a bus error:

$ openjade demo.sgm
Bus error

This is on my 10.4 Tiger system with the updated openjade port.

[raimue (Rainer Müller)]

I can confirm the issue on Mac OS X 10.5.4 Leopard.

Here is a backtrace:

$ gdb openjade
...
(gdb) r -v /opt/local/share/sgml/openjade/demo.sgm
Starting program: /opt/local/bin/openjade -v /opt/local/share/sgml/openjade/demo.sgm
Reading symbols for shared libraries +++++++++..... done
/opt/local/bin/openjade:I: "openjade" version "1.3.2"
/opt/local/bin/openjade:I: "OpenSP" version "1.5.2"

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x00437c4e in OpenSP::ParsedSystemId::unparse ()
(gdb) bt
#0  0x00437c4e in OpenSP::ParsedSystemId::unparse ()
#1  0x001cb811 in OpenJade_DSSSL::DssslApp::processSysid ()
#2  0x00425a4c in OpenSP::EntityApp::processArguments ()
#3  0x0040dafb in OpenSP::CmdLineApp::run ()
#4  0x000029cc in main ()

[raimue (Rainer Müller)]

I went ahead and filed a ​ticket upstream at sf.net.

[tom.duck@…]

Thanks for confirming and submitting the upstream report, raimue.

[(none)]

Milestone Port Bugs deleted

[blb@…]

The ​Debian bug gives a method to run it without crashing (and it looks like all they did was update documentation to close the bug):

openjade -o demo.xml -d /opt/local/share/sgml/openjade/demo.dsl /opt/local/share/sgml/openjade/demo.sgm

[raimue (Rainer Müller)]

Cc Me!

[lockhart (Thomas Lockhart)]

The demo works if the demo catalog is included in the invocation:

sudo openjade -d /opt/local/share/sgml/openjade/demo.dsl /opt/local/share/sgml/openjade/demo.sgm

which can be determined by a bit of google searching. Problem reports (and solutions) go back at least 13 years and across various target environments.

I believe that this problem report should be retired.