when you develop a program , you have an uml model and source code.

         the uml model is to visualize structural ralatoinshoips,interesting interactoin.

          now objext slicing can show you state diagram at runtime.

        it means if there;'s no source code ..we can analize and visualize the victim software.

          there are 1600 kinds of java open project in this sourceforge.

          then, we can get some design document and other inforamtion about those projects.

        and met interresting project then get invove to the project.

          but ....crash!

          the project source code so large. and complex ...

          we  are tired of looking hell code.

          additional problem is occur if you don't give up.

          you may confuesd what part would be nice to start.

        i'm also had this problem. last and this year ..I would love to join jxta,mugu project.

          but It can't be.

          those project so complex to join.

          (past year I'll love to print whole source code and read it .! but heck! it 's so hard to do)

          so I realize that if we trace objext(its field,method) when we run the program that want to hack              

          it would be good to hacking the victim s/w.

        and easy to join.

        so write xml structure to trace.

          ---------------here goes xml structure------------

        <?xml version='1.0' ?>

        <!DOCTYPE picture [

        <!ELEMENT picture (entry*)>

        <!ELEMENT entry (caller,threadno,identifier,name,method,return,location)>

        <!ELEMENT caller (#PCDATA)>

        <!ELEMENT threadno (#PCDATA)>

        <!ELEMENT identifier (#PCDATA)>

        <!ELEMENT name (#PCDATA)>

        <!ELEMENT method (#PCDATA)>

        <!ELEMENT return (#PCDATA)>

        <!ELEMENT location (#PCDATA)>

        ]>

        ------------------------------------------------------

             now we create this state.xml  using visivue.

          visivue excute program what you want to hack ...

          then trace your program and write state.xml.

          (if the program use GUI you can trace what you want

           ex. click the menubar or do other act this will be traced into state.xml)

          ooops!

          then run visualizer.

          shell> java -cp  . StateDigram

          finally you can see the state diagram.

         (new () keyward means created Object)

hacked by pio 2001.8.17 at pohang powered by gwangju linux user group(http://kjlug.sarang.net)