In the very few times I've ever been in the need of using flare/flasm,
I never really had much of success...
most probably because the samples were heavily obfuscated.
Not mentioning also that the above don't work with newer versions of Flash...
For basic info and/or statistics gathering related tasks,
either
swfdump (from the swftools package) or
swf_dump (from the sswf package),
both already mentioned above...do the job fine in most of the cases.
There also appear to be a few other open source "solutions" out there lately,
when it comes to Flash debugging/disassembling...if anyone really interested can search here:
http://osflash.org/projectsMost probably the most interesting one is the ActionScript 3 "AbcDump" decompiler,
which also has been already mentioned above...
To keep it short,a sum up of the above...
Current open source solutions at the moment,
are lacking way too many features to be usable in a "fire-up-and-go" way.
And that's exactly the "gap" that gets filled from the various commercial decompilers (ie.Sothink)...
Unless of course someone is really willing to spend his/her time,
both for reading Adobe's specs for the various versions,
and to also study/exercise manually the various Flash protectors which are sold out there...
(again,check Woodmann's threads above to get a basic idea...
it's certainly not an easy task for inexperienced people).
tjs's warning though is more than important...
Pretty much as with Olly etc...only under a spare test machine/virtualized enviroment etc.