Bug 17327 - [DllImport] are not recursively scanned and "deep" symbols might get stripped
Summary: [DllImport] are not recursively scanned and "deep" symbols might get stripped
Status: VERIFIED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: 7.2.1
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2014-01-20 09:50 UTC by Sebastien Pouliot
Modified: 2014-03-21 08:04 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
VERIFIED FIXED

Description Sebastien Pouliot 2014-01-20 09:50:36 UTC
Only the type and the first level (NestedType) are presently processed. That should be recursive so deeply nested types are scanned too.

Reference:
http://forums.xamarin.com/discussion/12426/link-all-assemblies-strips-my-static-library-symbols-for-release-builds
Comment 1 Sebastien Pouliot 2014-01-20 10:45:25 UTC
Fixed in master c712628fc5f6526ce3e7e5a672303aa3622653d1

QA: unit test added in the same revision

p.s. Gouri, can you check (or add if needed) if 'linksdk' test is executed from a "Release" build on the devices (that will allow the unit test to be executed in the right conditions). Thanks
Comment 3 Nischal 2014-03-21 08:04:29 UTC
As per Comment#1 Unit test has added.

Hence, changing the status to Verified.