Closed GoogleCodeExporter closed 8 years ago
Hi Adam,
we would like to reproduce the steps which resulted in the specified error. Are
you able to share the executable with us that results in the error described
and the exact steps that you took for the error to appear? Also it would be
interesting to know if the source IDB has been completely cleaned before the
executable was loaded into the BinNavi database. We are looking forward to your
answer.
Best Regards,
Tim Kornau
Original comment by timkor...@google.com
on 4 Oct 2012 at 12:40
Sadly I am not able to provide the binary, because it is in development right
now. I did not explicitly clean up the IDB before I loaded it, so I just now
reloaded the IDB after I closed/garbage collected it. The same issue persists.
Original comment by adam.ham...@gmail.com
on 4 Oct 2012 at 3:06
Hi Adam,
Ok if you can not provide the IDB please specify what kind of operation you did
perform using the debugger. Did you use the trace mode? Did you use a normal
break point? Did you do anything else of importance? What is the user you
started the debugger with? Did you try to debug any for of malware which has
any protection mechanisms in place?
To clarify on cleaning up the IDB, I did not mean you to collect the garbage in
the IDB but to make sure that there are no significantly large "red" spots in
the disassembly where IDA did not define a function.
Best Regards,
Tim Kornau
Original comment by timkor...@google.com
on 4 Oct 2012 at 3:20
- I was attempting to trace through a program
- I set a normal breakpoint (CTRL + right-click)
- I am remote debugging; the remote debugging instance is running as
administrator, the local BinNavi instance is running as a normal user
- No protection is present on the binary (not malware or anything like that)
- There are not any 'bad' sections in the IDB; IDA was able to dissasemble the
program fine.
Original comment by adam.ham...@gmail.com
on 4 Oct 2012 at 3:33
Hi Adam,
could you please send your licence key to zynamics-support@google.com. We will
check if you are still in the upgrade period for our new release and send you a
new version. Hopefully this will then resolve the problem. If the problem still
persists we will need to find a file which has similar behavior, and that you
can share with us.
Best Regards,
Tim Kornau
Original comment by timkor...@google.com
on 4 Oct 2012 at 3:43
Original comment by timkor...@google.com
on 9 Oct 2012 at 10:02
Original comment by timkor...@google.com
on 28 Apr 2015 at 8:28
Original issue reported on code.google.com by
adam.ham...@gmail.com
on 4 Oct 2012 at 12:33