Bug 490447 - Expression service - Looking for pseudo_types takes the wrong one
Summary: Expression service - Looking for pseudo_types takes the wrong one
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.4   Edit
Assignee: Project Inbox CLA
QA Contact: Eugene Tarassov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-25 12:09 EDT by xavier pouyollon CLA
Modified: 2016-05-26 04:31 EDT (History)
0 users

See Also:

Attachments
Logs and test .vxe (2.04 MB, application/gzip)
2016-03-25 12:10 EDT, xavier pouyollon CLA 		no flags Details
Description of problem and analysis. (85.35 KB, application/pdf)
2016-03-25 12:11 EDT, xavier pouyollon CLA 		no flags Details
View All 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-03-25 12:09:37 EDT 
Hi Eugene,

Can you please take a look at the attached tar files and the attached PDF ?

A PDF was easier to explain what happens. 
I've attached the logs from the IA64 session and the ARM session as well as the .vxe (in build_logs).

Here, we are stopped somewhere that matches the debugger_test.o compil unit.
There is a search against "true" type and it returns a type that is OUTSIDE of the compilation unit. 

Then our shell compares the types and they don't match.
To me, the issue would lie in symbols_elf, when processing the pseudo_symbols.

Thanks !
Xavier.
Comment 1 xavier pouyollon CLA 2016-03-25 12:10:34 EDT 
Created attachment 260580 [details]
Logs and test .vxe
Comment 2 xavier pouyollon CLA 2016-03-25 12:11:02 EDT 
Created attachment 260581 [details]
Description of problem and analysis.
Comment 3 Eugene Tarassov CLA 2016-03-25 21:55:53 EDT 
Yes, symbols reader should search current unit first, before searching public names.

Fixed.
Thanks!
Comment 4 xavier pouyollon CLA 2016-03-29 08:21:03 EDT 
Thanks, it works great in my case !

Best Regards,
Xavier.
Comment 5 Martin Oberhuber CLA 2016-05-26 04:31:35 EDT 
Setting target milestone for all RESOLVED/FIXED recently to 1.4

Please comment if any fix was actually backported or the target milestone would be incorrect for any other reason.