Jump to content

Strife function coverage near 100%


Recommended Posts

Thought I'd post an update about my progress with Strife. Almost all that's left is determining the rest of the codepointer functions (about a third of them have been matched up to their known purpose so far, and all of them have been worked on to some degree).

There are also a few "corner case" functions in various modules that are difficult to crack. I'm trying to chip away at them bit by bit. The mobj_t structure has been mapped completely (and contained basically no surprises), but the player_t struct remains to be done and is six times larger than mobj_t x_x

Here's a complete list of the functions from IDA Pro. Those named "sub_#####" are ones that have yet to be positively identified. Names of all original Strife functions are naturally speculative, but most that are named I am at least 90% certain of their function. All functions after the dashed line are part of DMX, libc, or Watcom's crt0 and are therefore not important and won't be worked on any further.

http://eternity.mancubus.net/text/strifefuncs20090504.txt

* I probably better mention the helpfulness of Kaiser here, who has identified many of the functions, including most of the codepointers ;) We have been pleased to a see a nearly line-to-line match with the source of svStrife repeatedly.

Share this post


Link to post
Quasar said:

Names of all original Strife functions are naturally speculative


I bet they weren't named A_HideDecepticons, A_ItBurnsItBurns or A_PlayerExtraCrispy.

Share this post


Link to post
Quasar said:

Kaiser and I have figured out all but four of the codepointers now ^_^


When I get on IRC, show me the remaining four codepointers.

Share this post


Link to post
Quasar said:

Kaiser and I have figured out all but four of the codepointers now ^_^


Okay, now we got all the codepointers, excluding the unused ones.

Share this post


Link to post

As far as I know, only one is now unknown, and it is unused ;)

EDIT: It wasn't a codepointer after all. It is a P_ThrustMobj function which appears to have been inlined, and thus has no xrefs.

I now count a mere 33 functions in the entire program that have not been identified. This is not implying that we know all the specifics in the functions that HAVE been identified, but this is true for a vast majority of them at least :)

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...