Here's a patch that should do what you want: http://bazaar.launchpad.net/~piersh/swfmill/fixes/revision/294
after you've built that, you should be able to add the following to your
MethodBody...
<MethodBody>
<code>
...
<UnknownOpCode id="0xfe">
<data>{optional, base64-encoded op-code body}</data>
</UnknownOpCode>
...
</code>
</MethodBody>
Otherwise, if you don't want to require a custom swfmill, you could encode
the whole 'DoABCDefine' tag as base64-encoded blob like this:
<UnknownTag id="0x52">
<data>{base64-encoded tag content}</data>
</UnknownTag>
You could use the patch above to create such a swf, using swfmill's -V
switch to tell you where in the file it put the tag. Make sure the swf you
create is uncompressed, then the addresses shown are relative to 8 bytes
from the start of the file. Look for the '0xfe' byte and the corresponding
start byte of the next tag. Extract and base64-encode the blob and stick it
in your xml.
Hope that helps!
Piers.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Sandro Santilli
Sent: Thursday, March 31, 2011 6:30 AM
To: [email protected]
Subject: [swfmill] Specifying opcodes by number
I'm looking for a way to produce a testcase for a Gnash bug where Gnash
would choke on opcode 0XFE.
But I see that swfmill last supported opcode is 0xF3 ("OpTimestamp").
Can op codes be specified literally in .xml files rather than by symbolic
name ? Ideally this would let me write the testcase in a way to be supported
by versions back to 0.2.12-2 (shipped in debian lenny).
Thanks in advance for any tips.
--strk;
() Free GIS & Flash consultant/developer
/\ http://strk.keybit.net/services.html
_______________________________________________
swfmill mailing list
[email protected]
http://osflash.org/mailman/listinfo/swfmill_osflash.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ swfmill mailing list [email protected] http://osflash.org/mailman/listinfo/swfmill_osflash.org
