Bug 500746 - Commit 02cb9598f643cf0 introduces a major regression with vxWorks 7
Summary: Commit 02cb9598f643cf0 introduces a major regression with vxWorks 7
Status: RESOLVED FIXED
Alias: None
Product: TCF
Classification: Tools
Component: Agent (show other bugs)
Version: 1.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.5   Edit
Assignee: Project Inbox CLA
QA Contact: Eugene Tarassov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-02 09:46 EDT by xavier pouyollon CLA
Modified: 2017-05-19 05:30 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description xavier pouyollon CLA 2016-09-02 09:46:59 EDT 
Hi Eugene,

Before commit 02cb9598f643cf0 (Bug 499118), the vxWorks test suite ran fine. After it does not. Well, it fails with vxWorks runtime agent hasn't been updated too.

The vxWorks 7 test suite only works if BOTH the target agent AND host tcf-server value-add are in sync. 

The condition of failure are the following:

vxWorks target contains a TCF agent that has breakpoint.c.
All symbol management is done on host side.

OLD Target (breakpoint.c before 02cb9598f643cf0) and NEW value-add, the test suite blocks. I'm still a little unclear of why. It seems the event breakpoint status never comes, which makes the test suite fail.

NEW Target (breakpoint.c updated with 02cb9598f643cf0) and NEW value-add, the test suite works well.

We'd like a new value-add (so linenumbers.c, linenumber_elf.c after 02cb9598f643cf0) to work with old runtimes (that have breakpoint.c before 02cb9598f643cf0).

Because customer might update Workbench (the host tools) without updating their vxWorks kernel.

Can you add "backward" compatibility on this? 

Many Thanks !
Comment 1 Eugene Tarassov CLA 2016-09-02 16:16:09 EDT 
I have added compatibility check.
Fixed.
Thanks!
Comment 2 xavier pouyollon CLA 2016-09-05 08:15:06 EDT 
Works great ! Many thanks !