disasmwinnie / proxbbe Goto Github PK

Hello, I am trying to write a similar tool like tracer in your proxbbe. However, I could not record information in my callbacks. I am wondering if it is mandatory to output information in p_finished callbacks. Can I use stdout to output information in my callbacks?

e.g. INS_InsertCall(ins, IPOINT_AFTER, (AFUNPTR)cb ...)

Can I use stdout in cb?

Basically address point 6 from the limitations section in the Readme:

6. The file code/analyzer/utils/pin_iclass.rb contains a mapping of PIN instructions, which varies throughout PIN-releases. At the moment it is partly created by "intelligent grep-ing" and partly by hand. Writing a hacky script to automate this task, would make porting to newer versions easier.

I see three ways to approach this:

• Write a helper scripts which parses pins iclass file and re-maps the instruction numbers in pin_iclass.rb
• Make the analyzer take a cmd argument to parse PINs corresponding header file.
• parse the string mnemonics from the trace files.

The last one is not very efficient, which is why the number was implemented in the first place. The second is at the moment my favorite.

Also, as additional TODO: change readme to highlight that wrong PIN versions also break the analyzer. Atm, it's mentioned elsewhere in the doc.

I have made it to run "pin -t traceer.so -- wget https://json.com" and got a trace
file. However, while analyzing it using the Ruby script, I met a Nil Error, i.e.,
/proxbbe/analyzer/taint_engine/taint_engine.rb:725:in handle_cmpsx': undefined method []' for nil:NilClass (NoMethodError)
Is this due to the unhandled cmpsx instruction?

Hello, when I read this piece of codes, I felt confused. I am wondering if you can help me understand this.

ThreadTrace*
get_tls(THREADID tid)
{
  return static_cast<ThreadTrace*>(PIN_GetThreadData(tls_key, tid));
}

When using static_cast to cast threadData to pre-defined ThreadTrace, are we supposed to following some specific rules to define ThreadTrace, or it can be any kind of structs?