[BUG] outputdir ignored

pkt
2004-08-05
2004-08-05
  • Jason Martin

    Jason Martin - 2004-08-05

    The outputdir option is interpreted as a filename prefix as opposed to a directory.

     
    • Nobody/Anonymous

      hmm? did you specify it as a filename prefix or a directory ? if you specify it without a trailing /, pkt will treat it as a filename prefix.
      anyway, i didnt recv your .pkt file with the bug ...did you email it to me as an attachment (<1 meg) ?
      also please post your java -version output.
      thx.

       
    • Jason Martin

      Jason Martin - 2004-08-05

      Ahh I see. Might want to make it check to see if outputdir is a dir first before assuming it is a prefix.

      I sent the pkt file before but I'll resent it. It is < 1MB.

      Java version:
      java version "1.4.1"
      Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)
      Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode)

       
    • Nobody/Anonymous

      i recvd it but i dont see the error.

       
      • Jason Martin

        Jason Martin - 2004-08-05

        Am I correwct that "Packet 55" is the packet with the -55.pkt suffix?

        The output I am getting is:
        [snip]
        PKT> Unpacking uncompressed packet 53 ...
        PKT> Verifying packet 53 is valid XML ...
        PKT> Verified packet 53 has a valid length.
        PKT> Packet 53 is a valid packet. Writing... misc/Qdata.QSD.gz
        PKT> Unpacking uncompressed packet 54 ...
        PKT> Verifying packet 54 is valid XML ...
        PKT> Verified packet 54 has a valid length.
        PKT> Packet 54 is a valid packet. Writing... misc/group.tif.gz
        PKT> Unpacking uncompressed packet 55 ...
        PKT> Verifying packet 55 is valid XML ...
        Exception in thread "main" java.lang.InternalError: fillbuf
                at org.apache.crimson.parser.InputEntity.parsedContent(InputEntity.java:545)
                at org.apache.crimson.parser.Parser2.content(Parser2.java:1826)
                at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
                at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
                at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
                at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
                at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
                at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
                at org.jdom.input.SAXBuilder.build(SAXBuilder.java:370)
                at org.jdom.input.SAXBuilder.build(SAXBuilder.java:724)
                at org.jdom.input.SAXBuilder.build(SAXBuilder.java:703)
                at net.sf.pkt.b.c.a(Unknown Source)
                at net.sf.pkt.b.c.a(Unknown Source)
                at net.sf.pkt.PKTENGINE.a(Unknown Source)
                at net.sf.pkt.PKTENGINE.bridge(Unknown Source)
                at net.sf.pkt.PKTCLI.a(Unknown Source)
                at net.sf.pkt.PKTCLI.main(Unknown Source)

         
    • Nobody/Anonymous

      yup. thats the right packet.
      i suggest retrying with the sun JVM. the blackdown JVM has all kinds of strange problems.

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks