[taste-users] SIGSEGV in Application

[Gert Caspersen <gec@xxxxxxxxx>]

                Dear Taste Users,

 

I now have ended up with an application that terminates due to a segmentation violation (see enclosed extract from our problem tracking system).

 

Any suggestions are highly appreciated….

 

                Regards,

 

                                Gert

 

Gert Caspersen
Senior Engineer, Project Manager
Space Projects (DK)
Space

Terma A/S
Vasekær 12
2730 Herlev
Denmark

T +45 8743 6000
T +45 4594 9653 (direct)
F +45 8743 6001
E gec@xxxxxxxxx
W www.terma.com

---

Attention:
This e-mail (and attachment(s), if any) - intended for the addressee(s) only - may contain confidential, copyright, or legally privileged information or material, and no one else is authorized to read, print, store, copy, forward, or otherwise use or disclose any part of its contents or attachment(s) in any form. If you have received this e-mail in error, please notify me by telephone or return e-mail, and delete this e-mail and attachment(s). Thank you.

Title: [#MBCODE-12] Segmentation Fault Raised in Demonstrator

<< Back to previous view

[MBCODE-12] Segmentation Fault Raised in Demonstrator Created: 2012.06.06  Updated: 2012.06.06
Status:	Open
Project:	Model Based Component Development
Component/s:	None
Affects Version/s:	None
Fix Version/s:	None
Security Level:	Public Issue (Issue visible to all project affiliates (i.e. members and observers).)

Type:	Problem Report	Priority:	Major
Reporter:	Gert Caspersen	Assignee:	Poul Hougaard
Resolution:	Unresolved	Votes:	0
Labels:	None
Remaining Estimate:	0h
Time Spent:	6h
Original Estimate:	Not Specified
Environment:	Revision 142 TASTE Build 120516

Description

A segmentation fault is raised by the demonstrator prototype when a service report is submitted to ground.

The error is raised upon return from the following function:

PolyORB_HI.Thread_Interrogators

procedure Store_Received_Message
     (Thread_Interface : Thread_Interface_Type;
      From             : Entity_Type;
      Time_Stamp       : Ada.Real_Time.Time    := Ada.Real_Time.Clock)
   is
   begin
      pragma Debug (Put_Line (Verbose, CE & ": Store_Received_Message"));

      Global_Queue.Store_In
        ((From, Interface_To_Stream (Thread_Interface)), Time_Stamp);
   end Store_Received_Message;

The call to Global_Queue.Store_In appears to be completed successfully.

The last output from the debugger is:

polyorb_hi_generated.activity.process_package_ground_interrogators.store_received_message (thread_interface=<value optimized out>, from=globalpartition_obj102_thegenerator_k, time_stamp=1338979527.95152) at /home/assert/tool-inst/include/ocarina/runtime/polyorb-hi-ada/polyorb_hi-thread_interrogators.adb:1370
(gdb) step
[New Thread -1222806176 (LWP 20887)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222806176 (LWP 20892)]
0x00000000 in ?? ()

It appears that a context switch is taking place, leading to the SIGSEGV signal.

Comments

Comment by Gert Caspersen [ 2012.06.06 13:28 ]

Increase of stack size to 1000KB (though parameter --stack to script assert-builder-ocarina.py does not eliminate the problem.

Generated at Wed Jun 06 13:44:57 CEST 2012 by Gert Caspersen using JIRA 4.4#649-r158309.