From Terry.O'Laughlin at ipc.com Wed Dec 1 00:12:45 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Wed Dec 1 00:12:49 2010 Subject: [xsde-users] Moved application code to different XSDe build environment, get a runtime version mismatch error Message-ID: Hi, I moved my message parsers from the latest 3.2b1 version to an older version (3.1.? or first 3.2 version). Get a runtime version mismatch. Why does the generated code still generate the version number of my other build? Even when I clean the environment first? What file is hanging around that tells the xsde compiler to generate code with the old runtime version, not the latest? I rebuilt the entire library and examples and have no problem. So why my newly added directory with my message parsers having this problem? C:\xsde_v3.2_win32_vc9\examples\cxx\hybrid\MessageParsers>nmake -f nmakefile Microsoft (R) Program Maintenance Utility Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. cl.exe -D_CRT_SECURE_NO_DEPRECATE /I..\..\..\..\libxsde /nologo /W3 /EHs /c /TP driver.cxx /Fodriver.obj driver.cxx c:\xsde_v3.2_win32_vc9\examples\cxx\hybrid\messageparsers\messages.hxx(27) : fatal error C1189: #error : XSD/e runtime version mismatch NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe"' : return code '0x2' Stop. Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. [cid:green-logo32de.jpg]Please consider the environment before printing this email. -------------- next part -------------- A non-text attachment was scrubbed... Name: green-logo32de.jpg Type: image/jpeg Size: 1268 bytes Desc: green-logo32de.jpg Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101201/5f4e1163/green-logo32de.jpg From Terry.O'Laughlin at ipc.com Wed Dec 1 09:26:28 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Wed Dec 1 09:28:05 2010 Subject: [xsde-users] Moved application code to different XSDe build environment, get a runtime version mismatch error In-Reply-To: References: Message-ID: Sorry, I found my error. I have a batch file that generates the code, it was hardcoded to the wrong version of the compiler. So I understand why I was having the problem. Sorry, Cheers, Terry O' ----------------------------------------------------- Please consider the environment before printing this email. -----Original Message----- From: xsde-users-bounces@codesynthesis.com [mailto:xsde-users-bounces@codesynthesis.com] On Behalf Of O'Laughlin, Terry Sent: Wednesday, December 01, 2010 12:13 AM To: xsde-users@codesynthesis.com Subject: [xsde-users] Moved application code to different XSDe build environment, get a runtime version mismatch error Hi, I moved my message parsers from the latest 3.2b1 version to an older version (3.1.? or first 3.2 version). Get a runtime version mismatch. Why does the generated code still generate the version number of my other build? Even when I clean the environment first? What file is hanging around that tells the xsde compiler to generate code with the old runtime version, not the latest? I rebuilt the entire library and examples and have no problem. So why my newly added directory with my message parsers having this problem? C:\xsde_v3.2_win32_vc9\examples\cxx\hybrid\MessageParsers>nmake -f nmakefile Microsoft (R) Program Maintenance Utility Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. cl.exe -D_CRT_SECURE_NO_DEPRECATE /I..\..\..\..\libxsde /nologo /W3 /EHs /c /TP driver.cxx /Fodriver.obj driver.cxx c:\xsde_v3.2_win32_vc9\examples\cxx\hybrid\messageparsers\messages.hxx(27) : fatal error C1189: #error : XSD/e runtime version mismatch NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe"' : return code '0x2' Stop. Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. [cid:green-logo32de.jpg]Please consider the environment before printing this email. From boris at codesynthesis.com Wed Dec 1 10:25:24 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Dec 1 10:17:56 2010 Subject: [xsde-users] Serializing questions: Illegal namespace error & 'g1' namespace/prefix In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > 1. Why do I get this error, illegal namespace, when I try to serialize > an element from my schema? This has been fixed for the upcoming 3.2.0 release. Are you using 3.1.0? > 2. Why do I get the prefix/namespace 'g1:' added as an attribute to my > root element? (Here is my serialized output, with "crs" added for > readability) This is after you "fixed" Genx not to complain about (1), right? Well, that "fix" is not correct and the prefix you see is the symptom. Boris From boris at codesynthesis.com Wed Dec 1 10:33:36 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Dec 1 10:26:06 2010 Subject: [xsde-users] Re: Build fails with socket references not resolved in XSDe v3.2.b1 but builds fine in V3.2 In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > I'm perplexed. I get the following link errors when building with the beta > version of 3.2b (whatever the latest version I've been using). But I move > the build directory to build under V3.2, no problem, builds fine. I assume you mean V3.1(.0) here instead of V3.2. I don't see why you should get the link errors since XSD/e does not use any socket code, neither in 3.1.0 nor in 3.2.0.b1. The only thing I can think of is that you may have added some libraries (like winsock) to the LIBS variable in config.nmake for 3.1.0 but forgot to do the same for 3.2.0.b1. Can you show the linker command line for the successful build under 3.1.0? Boris From sir.costy at gmail.com Thu Dec 2 03:58:46 2010 From: sir.costy at gmail.com (Constantin Iacobescu) Date: Thu Dec 2 03:58:49 2010 Subject: [xsde-users] Does XSD/e works on iOS (iPhone SO) and does the C++/Hybrid support polymorphism? Message-ID: Does XSD/e works on iOS (iPhone SO) and does the C++/Hybrid support polymorphism? Till now have use the clasic XSD and C++/Tree for binding on Windows. But most of my code is multi (cross) platform and it is used on Microsoft Windows, Apple Mac OSX and Apple iOS. So just plan to pass to use the XSD/e for compatible coding. Actually have plan it long ago but before XSD/e was nor able to handle polymorphic schema. Does anyone made some like this before? mean multi (cross) platform binding including mobile ones. Does the XSD/e C++/Hybrid know to work with polymorphism now? Best Regards, Constantin Iacobescu From boris at codesynthesis.com Thu Dec 2 07:17:55 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Dec 2 07:10:51 2010 Subject: [xsde-users] Re: Using minimal configuration, problem parsing using multiroot example In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > I am getting a parser error after completion of parsing (doc_p.parse), > error 2, xml error, ?invalid token?. Here is the relevant parts of your code: char buf[4096] ; ... size_t s = fread (buf, 1, sizeof (buf), f); ... doc_p.parse ( buf, sizeof(buf), true ); You allocate a buffer 4096 bytes long, then read some data into it, which has size 's'. Then you try to parse 4096 bytes of XML. Unless the XML file you are trying to parse is exactly 4096 bytes long, the buffer will contain garbage after the 's' bytes. If I change the last line in the above code to read as follows, the error goes away: doc_p.parse ( buf, s, true ); Boris From Terry.O'Laughlin at ipc.com Wed Dec 1 19:52:47 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Thu Dec 2 07:11:33 2010 Subject: [xsde-users] Using minimal configuration, problem parsing using multiroot example Message-ID: Skipped content of type multipart/related-------------- next part -------------- A non-text attachment was scrubbed... Name: driver.cxx Type: application/octet-stream Size: 6840 bytes Desc: driver.cxx Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101201/33ede279/driver-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: config.nmake Type: application/octet-stream Size: 7412 bytes Desc: config.nmake Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101201/33ede279/config-0001.obj From boris at codesynthesis.com Thu Dec 2 07:22:48 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Dec 2 07:15:27 2010 Subject: [xsde-users] Does XSD/e works on iOS (iPhone SO) and does the C++/Hybrid support polymorphism? In-Reply-To: References: Message-ID: Hi Constantin, Constantin Iacobescu writes: > Does XSD/e works on iOS (iPhone SO) and does the C++/Hybrid support > polymorphism? Yes to both questions. I suggest that you use the beta[1] (3.2.0.b1) for the upcoming release. There is a sample configuration file for iOS as well as documentation/examples that show how to work with polymorphic schemas. [1] http://www.codesynthesis.com/products/xsde/download.xhtml Boris From Terry.O'Laughlin at ipc.com Thu Dec 9 20:27:46 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Thu Dec 9 20:27:54 2010 Subject: [xsde-users] VxWorks Link errors --- strange things ... Message-ID: Hi Any advice would be great... VxWorks 5.5.1, gnu 2.97? (old compiler/linker), XSDe 3.2 beta I'm having undefined reference link errors building/linking to generate the filesystem for VxWorks. Here's how the week has played out so far... Same code, no changes... Built fine this past Monday, no link errors. Wednesday ... I had undefined reference errors on ALL, or most all of my serializer generated code. But not my parser generated code. Like 40-60 errors. Tonight regenerated my code from my schema, regenerated my object files ... This build now shows 4 link errors: ldppc -N -X -e _sysInit -Ttext 00010000 \ -o WAN vxworks/dataSegPad.o WAN.tmp ckversion.o ctdt.o -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM WAN.tmp: In function `RTCREvents_saggr::RTCREvents_saggr(void)': WAN.tmp(.text+0x379fb2): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' WAN.tmp(.text+0x379fb6): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' WAN.tmp(.text+0x37a25a): undefined reference to `xsde::cxx::serializer::validating::time_simpl::~time_simpl(void)' WAN.tmp(.text+0x37a25e): undefined reference to `xsde::cxx::serializer::validating::time_simpl::~time_simpl(void)' make: *** [WAN] Error 1 [bash-group_17.1_CyberTech_int]olaughlt@merlin:/usr/vobs/processor/WANX/pq> My xsde compiler build line: C:\xsde-3.2b\bin\xsde cxx-hybrid --generate-clone --generate-detach --show-sloc --generate-parser --generate-aggregate --generate-serializer --no-long-long --no-stl --no-exceptions --no-iostream messages.xsd Any suggestions? Has anyone seen this type of behavior? Cheers, Terry O' I'm thinking that my compiler flags or linker flags may need to be be updated... weird, no problems with my parser generated code. But it looks as though most or all of my serializer generated code is having this problem. VxWorks 5.5.1 Gnu 2.97 Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. [cid:green-logo6d73.jpg]Please consider the environment before printing this email. -------------- next part -------------- A non-text attachment was scrubbed... Name: green-logo6d73.jpg Type: image/jpeg Size: 1268 bytes Desc: green-logo6d73.jpg Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101209/fb39c895/green-logo6d73.jpg From Terry.O'Laughlin at ipc.com Thu Dec 9 20:32:19 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Thu Dec 9 20:32:23 2010 Subject: [xsde-users] Example of using hexBinary with XSDe hybrid Message-ID: Hi, I'm trying to figure out how to serialize and parse using the XML type hexBinary. Sort of confusing to me. I'm trying to transmit a 'bitMask' about 5-6 bytes long which shows an equipment configuration. I see the XSDe documentation shows that the XML buffer class is used as the interface, but not sure how to use the methods of this class. Not sure what primitive data class, string, char *, int, unsigned bytes, etc. that I can use to place data into this buffer. Appreciate the help, Cheers, Terry O' Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. [cid:green-logo13a6.jpg]Please consider the environment before printing this email. -------------- next part -------------- A non-text attachment was scrubbed... Name: green-logo13a6.jpg Type: image/jpeg Size: 1268 bytes Desc: green-logo13a6.jpg Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101209/d1bee892/green-logo13a6.jpg From boris at codesynthesis.com Fri Dec 10 06:32:23 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Dec 10 06:24:39 2010 Subject: [xsde-users] Example of using hexBinary with XSDe hybrid In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > I'm trying to figure out how to serialize and parse using the XML > type hexBinary. Sort of confusing to me. I'm trying to transmit > a 'bitMask' about 5-6 bytes long which shows an equipment configuration. > I see the XSDe documentation shows that the XML buffer class is used > as the interface, but not sure how to use the methods of this class. > Not sure what primitive data class, string, char *, int, unsigned bytes, > etc. that I can use to place data into this buffer. The xml_schema::buffer class is a simple wrapper for the raw data buffer concept. Here is how you can use it: char* data = ... // some data size_t data_size = ... // number of bytes in data xml_schema::buffer b (data, data_size); // 'b' now has a copy of data char* p = b.data (); size_t n = b.size (); assert (n == data_size); assert (memcmp (data, p, n) == 0); Boris From boris at codesynthesis.com Fri Dec 10 06:37:14 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Dec 10 06:29:29 2010 Subject: [xsde-users] Re: VxWorks Link errors --- strange things ... In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > ldppc -N -X -e _sysInit -Ttext 00010000 \ > -o WAN vxworks/dataSegPad.o WAN.tmp ckversion.o ctdt.o -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM > WAN.tmp: In function `RTCREvents_saggr::RTCREvents_saggr(void)': > WAN.tmp(.text+0x379fb2): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' These symbols should be defined in libxsde.a. Try to add it to the linker command line, after WAN.tmp: ldppc -N -X -e _sysInit -Ttext 00010000 \ -o WAN vxworks/dataSegPad.o WAN.tmp path/to/libxsde.a ckversion.o ctdt.o \ -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM Boris From Terry.O'Laughlin at ipc.com Fri Dec 10 09:18:19 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Fri Dec 10 09:18:30 2010 Subject: [xsde-users] RE: VxWorks Link errors --- strange things ... In-Reply-To: References: Message-ID: Hi Boris, Is it that there is a positional requirement to add after WAN.tmp? We have a lot of libraries that we add. It appears that if I move the position in the list of libs to link against, I get differing errors. I'll check into this with our VxWorks experts. Cheers, Terry O' ----------------------------------------------------- Please consider the environment before printing this email. -----Original Message----- From: Boris Kolpackov [mailto:boris@codesynthesis.com] Sent: Friday, December 10, 2010 6:37 AM To: O'Laughlin, Terry Cc: xsde-users@codesynthesis.com Subject: Re: VxWorks Link errors --- strange things ... Hi Terry, O'Laughlin, Terry writes: > ldppc -N -X -e _sysInit -Ttext 00010000 \ > -o WAN vxworks/dataSegPad.o WAN.tmp ckversion.o ctdt.o -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM > WAN.tmp: In function `RTCREvents_saggr::RTCREvents_saggr(void)': > WAN.tmp(.text+0x379fb2): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' These symbols should be defined in libxsde.a. Try to add it to the linker command line, after WAN.tmp: ldppc -N -X -e _sysInit -Ttext 00010000 \ -o WAN vxworks/dataSegPad.o WAN.tmp path/to/libxsde.a ckversion.o ctdt.o \ -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM Boris DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. From boris at codesynthesis.com Fri Dec 10 11:14:49 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Dec 10 11:07:04 2010 Subject: [xsde-users] Re: VxWorks Link errors --- strange things ... In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > Is it that there is a positional requirement to add after WAN.tmp? Yes, when linking to static libraries, order is important. You need to place libxsde.a after all the object files and libraries that use it. Another thing that you may want to check is that the libxsde.a library as well as the generated code and your source code are all compiled with the same options, particularly when it comes to the debug/optimization options. Boris From Terry.O'Laughlin at ipc.com Wed Dec 15 23:21:55 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Wed Dec 15 23:22:00 2010 Subject: [xsde-users] VxWorks crashes when first starting parse Message-ID: Hi, We have attempted with our code for the very first time, to parse an incoming message using XSDe as the XML parser tool. We are not exactly sure, but it appears the crash occurs at the beginning of the document_pimpl::parse() function. We can't be exactly sure,but this is the calling method. Our parsing design follows the 'multi-root' parser method. We subclass 'document_pimpl' and override the methods; start_root_element, and end_root_element. It appears that in the 'start_root_element' we determine the 'name' of the root element correctly. In our specific case, with code snippet included below, we are trying to parse a 'ConnectRequestAck' message. With this design, this is where the 'pre()' function is called on the ConnectRequestAck_paggr object, then we return the ConnectRequestAck root parser which ends the 'start_root_element' function. Our crash occurs sometime after determining the 'name'. We commented out the 'pre()' but we still crashed... So any ideas why on VxWorks 5.5.1 this would happen? It seems like the crash results from trying to free mememory? We haven't performed a detailed analysis to know exactly which object and function where the exception occurred. Hopefully we'll do that first thing tomorrow morning (Thurs am). So we took the input XML data, ran it successfully through our Windows-based parser with no problem. At least it appeared to have no problem. So not sure if that is an 'apples-to-apples' test. I've been parsing our messages on Windows for several weeks now. This is the first time after integrating the parser into our VxWorks environment to test this functionality. So we were also thinking that if you could give us some pointers of where to follow the underlying parser code, where we could insert printf statements? We at present are not using a debugger and hadn't planned on it, so we've been debugging using printfs. Appreciate the help, Cheers, Terry O' virtual xml_schema::parser_base* #ifndef XSDE_POLYMORPHIC start_root_element (const ro_string& ns, const ro_string& name) #else start_root_element (const ro_string& ns, const ro_string& name, const char* /* xsi:type */) #endif { printf("Start Root Element \n"); if (name == connectRequest_parser.root_name ()) { connectRequest_parser.pre (); return &connectRequest_parser.root_parser (); } else if (name == connectRequestAck_parser.root_name ()) { printf("Start Root Element: connectRequestAck parser \n"); //connectRequestAck_parser.pre (); // printf("Start Root Element: connectRequestAck parser PRE \n"); printf("Start Root Element: connectRequestAck parser PRE ++++++++ \n"); return &connectRequestAck_parser.root_parser (); } else if (name == sessionRequest_parser.root_name ()) { sessionRequest_parser.pre (); Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com [cid:green-logo32cf.jpg]Please consider the environment before printing this email. ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. -------------- next part -------------- A non-text attachment was scrubbed... Name: green-logo32cf.jpg Type: image/jpeg Size: 1268 bytes Desc: green-logo32cf.jpg Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101215/f708a6ff/green-logo32cf.jpg From Terry.O'Laughlin at ipc.com Wed Dec 15 23:28:21 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Wed Dec 15 23:28:24 2010 Subject: [xsde-users] VxWorks Linking problems -- Using XML datatype 'Time' generates undefined references Message-ID: Hi, Using VxWorks 5.5.1, gnu C/C++ 2.72? XSDe 3.2b1 In our schema, defined an attribute as 'time'. Get the following link errors. Redefining the time to a positive integer, links/builds fine. (Come to think of it, on windows, the 'time' datatype links/builds fine. I think this may have to do with VxWorks/gnu, and perhaps being a beta?) ldppc -N -X -e _sysInit -Ttext 00010000 \ -o WAN vxworks/dataSegPad.o WAN.tmp ckversion.o ctdt.o -T /usr/mx/3rdparty/vw5.5/powerpc_qos/target/h/tool/gnu/ldscripts/link.RAM WAN.tmp: In function `RTCREvents_saggr::RTCREvents_saggr(void)': WAN.tmp(.text+0x6a22ba): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' WAN.tmp(.text+0x6a22be): undefined reference to `xsde::cxx::serializer::validating::time_simpl::time_simpl(void)' WAN.tmp(.text+0x6a2562): undefined reference to `xsde::cxx::serializer::validating::time_simpl::~time_simpl(void)' WAN.tmp(.text+0x6a2566): undefined reference to `xsde::cxx::serializer::validating::time_simpl::~time_simpl(void)' make: *** [WAN] Error 1 p.s. All of the link errors I reported a week ago, was my fault for having extra tabs and/or spaces in the makefile. Using a compiler/linker that's 15 yrs old tends to have these type of odd behaviors. Terry O'Laughlin Sr. Software Engineer IPC TS Engineering Alliance Sustaining Dept. 777 Commerce Drive Fairfield, CT 06825 phone: 203-339-7987 fax: 203-339-7809 www.ipc.com Terry.O'Laughlin@ipc.com [cid:green-logo49f7.jpg]Please consider the environment before printing this email. ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. -------------- next part -------------- A non-text attachment was scrubbed... Name: green-logo49f7.jpg Type: image/jpeg Size: 1268 bytes Desc: green-logo49f7.jpg Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20101215/3d8fa520/green-logo49f7.jpg From boris at codesynthesis.com Thu Dec 16 05:48:20 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Dec 16 05:40:11 2010 Subject: [xsde-users] VxWorks Linking problems -- Using XML datatype 'Time' generates undefined references In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > In our schema, defined an attribute as 'time'. Get the following link > errors. Redefining the time to a positive integer, links/builds fine. Can you add the same attribute to the unmodified 'minimal' example (e.g., to the person type), try to build it with the supplied makefile, and see if you get the same link error? Boris From boris at codesynthesis.com Thu Dec 16 06:03:49 2010 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Dec 16 05:55:38 2010 Subject: [xsde-users] VxWorks crashes when first starting parse In-Reply-To: References: Message-ID: Hi Terry, O'Laughlin, Terry writes: > Our crash occurs sometime after determining the 'name'. Does it occur still in the start_root_element() function or after it has returned? > So any ideas why on VxWorks 5.5.1 this would happen? There could be multiple reasons, and it will be really hard to pin-point the problem without a stack trace. I remember one case where the proper floating point emulation options were not specified for the target hardware. Similarly, the same code worked fine on other platforms. > It seems like the crash results from trying to free mememory? What makes you think so? Boris From Terry.O'Laughlin at ipc.com Thu Dec 16 09:26:48 2010 From: Terry.O'Laughlin at ipc.com (O'Laughlin, Terry) Date: Thu Dec 16 09:27:00 2010 Subject: [xsde-users] VxWorks crashes when first starting parse In-Reply-To: References: Message-ID: It's hard to tell from just using printfs. We haven't looked at a stack trace yet. It definitately is getting into the start_root_element function as it's successfully identified the root name. Who calls the start_root_element function? Cheers, Terry O' ----------------------------------------------------- Please consider the environment before printing this email. -----Original Message----- From: Boris Kolpackov [mailto:boris@codesynthesis.com] Sent: Thursday, December 16, 2010 6:04 AM To: O'Laughlin, Terry Cc: xsde-users@codesynthesis.com Subject: Re: [xsde-users] VxWorks crashes when first starting parse Hi Terry, O'Laughlin, Terry writes: > Our crash occurs sometime after determining the 'name'. Does it occur still in the start_root_element() function or after it has returned? > So any ideas why on VxWorks 5.5.1 this would happen? There could be multiple reasons, and it will be really hard to pin-point the problem without a stack trace. I remember one case where the proper floating point emulation options were not specified for the target hardware. Similarly, the same code worked fine on other platforms. > It seems like the crash results from trying to free mememory? What makes you think so? Boris DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.