Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Titan » TTCN-3 Execution Error(Executing 3GPP IRAT test Cases)
TTCN-3 Execution Error [message #1785522] Mon, 16 April 2018 08:32 Go to next message
peeyush agrawal is currently offline peeyush agrawalFriend
Messages: 3
Registered: April 2018
Junior Member
Hi All

I am trying to execute 3GPP IRAT test cases.

My compilation and build for LTE_IRAT_Testsuite is successful. I get unexpected error "ttcn3_start: error: Something went wrong..." while executing test case from the suit.

I have titan core 5.5.0
Following is last portion of log where error happens

"Initializing module IMS_Procedures_Common.
Initializing module IMS_IP_Config.
Initialization of module IMS_IP_Config finished.
Initialization of module IMS_Procedures_Common finished.
Initialization of module IMS_Procedures_Registration finished.
Initializing module IMS_Procedures_CallControl.
ttcn3_start: error: Something went wrong...
Error: Unexpected end of HC connection from 127.0.0.1 [127.0.0.1].
Error: There is no HC connection after processing the configuration file.
Error during initialization. Cannot create MTC.
MC2> exit
Shutting down session.
Shutdown complete.

while executing
"expect -i $hc_id eof"
(procedure "error_cleanup" line 6)
invoked from within
"error_cleanup "Something went wrong... " 10"
invoked from within
"expect {
-i $mctr_id -re "MTC is created\..*\r\n" {
wait_mc_prompt
} -i $mctr_id -re "Cannot create MTC" {
error_c..."
(file "./ttcn3_start" line 257)
"
my .cfg configuration as follows
[LOGGING]
//LogFile := "TTCN_April16.log"
FileMask := LOG_ALL | TTCN_ERROR | TTCN_USER | TTCN_PORTEVENT | TTCN_DEBUG | TTCN_WARNING | TTCN_TESTCASE | TTCN_STATISTICS
ConsoleMask := LOG_ALL | TTCN_ERROR | TTCN_TESTCASE | TTCN_STATISTICS | DEBUG | MATCHING
SourceInfoFormat:= Single //or Stack
LogEntityName:= Yes
LogEventTypes:= Yes
LogSourceInfo := Yes

[EXECUTE]
LTE_IRAT_Testsuite.control

[TESTPORT_PARAMETERS]
*.*.mode := "advanced"
*.*.debugging := "yes"

[MAIN_CONTROLLER]
LocalAddress := 127.0.0.1
TCPPort := 10752
UnixSocketsEnabled := Yes

I am not getting any clue what is causing error. Please help!
Re: TTCN-3 Execution Error [message #1785626 is a reply to message #1785522] Tue, 17 April 2018 15:01 Go to previous messageGo to next message
Elemer Lelik is currently offline Elemer LelikFriend
Messages: 1120
Registered: January 2015
Senior Member
Hi peeyush,
based on the little information you provide it's impossible to tell what could be the problem.

Please try to start your executable not with the start script ttcn3_start, but step by step , as described in
https://www.eclipse.org/forums/index.php/t/1068004/


I general I'd recommend you start with something simple and get familiar with the tool first.


Best regards
Elemer






Re: TTCN-3 Execution Error [message #1785668 is a reply to message #1785626] Wed, 18 April 2018 08:06 Go to previous messageGo to next message
peeyush agrawal is currently offline peeyush agrawalFriend
Messages: 3
Registered: April 2018
Junior Member
Hi Elemer

I will try step by step procedure once, thanks for advice.

Regards
Peeyush
Re: TTCN-3 Execution Error [message #1785723 is a reply to message #1785668] Thu, 19 April 2018 01:55 Go to previous messageGo to next message
peeyush agrawal is currently offline peeyush agrawalFriend
Messages: 3
Registered: April 2018
Junior Member
Hi Elemer

I tried step procedure.

On Main Controller Terminal I got Following Log

Using configuration file: SSNITZ_Testsuite_2.cfg
MC@svp3glinux-Samsung-DeskTop-System: Unix server socket created successfully.
MC@svp3glinux-Samsung-DeskTop-System: Listening on IP address 127.0.0.1 and TCP port 10752.
MC2> cmtc
Waiting for HC to connect...
Error: HC connection from localhost [127.0.0.1] was refused because of incorrect version.

And on other Terminal I got following log

:~/TTCN3/LTE_IRAT_IWD_16wk49$ ./LTE_IRAT_Testsuite 127.0.0.1 10752
TTCN-3 Host Controller (parallel mode), version CRL 113 200/5 R5A
The address of MC was set to a local IP address. This may cause incorrect behavior if a HC from a remote host also connects to MC.
terminate called after throwing an instance of 'TC_Error'
./LTE_IRAT_Testsuite: Abort was called
./LTE_IRAT_Testsuite[0xc19c053]
/lib/x86_64-linux-gnu/libc.so.6(+0x36cb0)[0x7fbfb7637cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fbfb7637c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fbfb763b028]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x155)[0x7fbfb7f46535]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e6d6)[0x7fbfb7f446d6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e703)[0x7fbfb7f44703]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e922)[0x7fbfb7f44922]
./LTE_IRAT_Testsuite[0xc11d65a]
./LTE_IRAT_Testsuite[0xc154e05]
./LTE_IRAT_Testsuite[0xc155084]
./LTE_IRAT_Testsuite[0xc156182]
/lib/x86_64-linux-gnu/libc.so.6(+0x3c1a9)[0x7fbfb763d1a9]
/lib/x86_64-linux-gnu/libc.so.6(+0x3c1f5)[0x7fbfb763d1f5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfc)[0x7fbfb7622f4c]
./LTE_IRAT_Testsuite[0x54f242]
Aborted (core dumped)

Please the above command line output and suggest.

Thanks for all help

Regards
Peeyush

Re: TTCN-3 Execution Error [message #1785732 is a reply to message #1785723] Thu, 19 April 2018 06:57 Go to previous message
Elemer Lelik is currently offline Elemer LelikFriend
Messages: 1120
Registered: January 2015
Senior Member
Hi Peeyush,

OK that makes it clearer: the binary execution ends up in a segmentation fault. The reasons can be manifold: compiler fault, external C++ code, configuration issues.

Please upload your code, including Makefile and configuration file and we will take a look.

Best regards
Elemer




Previous Topic:Model Based Testing (MBT) and Eclipse Titan
Next Topic:Long Compilation time- OPC-UA
Goto Forum:
  


Current Time: Thu Mar 28 12:32:09 GMT 2024

Powered by FUDForum. Page generated in 0.04460 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top