As an "alternative" to the View profiles permissions module you've found yourself, you could also use the Rules module for this, as explained below.
Part 1: Create a 1st rule to assign role "Woman"
Rules Event: after a new user account is created
Check the value specified for your selection list (=
Woman), using these conditions:
(a) Entity has field (related to that selection list field), to make that field available to test its value.
(b) Perform a data comparison, to check if the value selected was
Refer to my answer to "How to specify a Rules condition related to select list values?" which includes a similar set of Rules conditions (though for entity "node" instead of "user" as you would need here).
Rules Action: grant the role "Woman".
Part 2: Create a 2nd rule to assign role "Man"
This is similar to what's detailed in Part 1 (use "Man" instead of "Woman").
Part 3: Optionally combine both rules in a single rule
The reason why you'd need 2 rules as detailed above, is that Rules does not allow to add "Rules Conditions" within the "Rules Actions". To get around that, you may want to use the Conditional Rules module using either Conditional (if/else) or Switch logic. For more details on that, refer to my answer to "How to access rules condition values in the rule event?".
Be aware: this module only has a beta release for D7, though it's used in over 8K sites (which makes it seem like a pretty robust module though).
If you're not familiar (enough/yet) with Rules, checkout the 32 (!!!) great, and free, video tutorials Learn the Rules framework.
PS: One of the advantages of using the Rules module, is that you can probably (actually: pretty sure) use it for lots of other features to implement in your site (which helps to avoid your site suffering "modulitis", aka "way too much contributed modules that slows down a site").