Comment 3 for bug 1551950

Some more testing shows this isn't really a regression - I can reproduce it with older parser versions (including latest 2.8.x from bzr), always using the "profile a" from the previous comment.

However, with 2.10 I first noticed this bug in the "real world", so maybe something made it more likely to happen.
I have several servers that still have apparmor_parser 2.8.4, and they never showed this bug (they all have an apache profile with quite some hats, and get the profiles updated/reloaded quite often)