2018-06-22 20:43 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000305Cheat Enginepublic2014-02-13 04:01
Assigned ToDark Byte 
Summary0000305: CE 6.3 - Trace does not trace into calls
DescriptionThese are examples of calls within the executable module itself (not kernel32.dll or any excluded module):
 - call XComEW.PIBGetInterface+1DA460
 - call edx
 - etc.

For some reason, CE does not trace into them - just as if the "Step over instead of single step" was checked. Except, it's not checked.

Issue 0000293 (new feature) and 0000302 (bug) may be related.
Additional Informationpure rev.2229_32&64bit.7z
TagsNo tags attached.
Attached Files

duplicate of 0000302resolvedDark Byte CE 6.3 - Trace does not include the first instruction on break 



Dark Byte (developer)

Is there a (conditional) jump in front of there? (Could be the jump is taken, but the instruction after it is disassembled instead)


Csimbi (reporter)

No, there's no jump before these.
I uploaded a sample pic.


Dark Byte (developer)

Ah ok. It's the same thing. The instruction after it is disassembled instead of the actual one
What you highlighted is actually push esi. The call is the next instruction
(E.g. note that int3 after the ret, that int3 is the ret)


Csimbi (reporter)

Are you saying that trace actually breaks into these calls but does not display them?


Dark Byte (developer)

Last edited: 2013-11-22 00:48

It does display them. Just click on the + sign before "inc [esi+18]" which is in fact "call edx"

same for "add esp,60" which is actually "call 01ee65b8"

(it's a bug yes, but just pointing out where the bug is, the disassembler address)


Csimbi (reporter)

Me blind, lol
Got it, thanks.


Dark Byte (developer)

fixed in the svn (a while ago)
same bug as 302

-Issue History
Date Modified Username Field Change
2013-11-20 23:10 Csimbi New Issue
2013-11-21 10:29 Dark Byte Note Added: 0000633
2013-11-21 17:54 Csimbi Note Added: 0000634
2013-11-21 17:54 Csimbi File Added: CE_CallSamples.png
2013-11-21 22:49 Dark Byte Note Added: 0000635
2013-11-22 00:36 Csimbi Note Added: 0000636
2013-11-22 00:46 Dark Byte Note Added: 0000637
2013-11-22 00:47 Dark Byte Note Edited: 0000637
2013-11-22 00:48 Dark Byte Note Edited: 0000637
2013-11-22 02:28 Csimbi Note Added: 0000638
2014-02-13 04:01 Dark Byte Note Added: 0000654
2014-02-13 04:01 Dark Byte Relationship added duplicate of 0000302
2014-02-13 04:01 Dark Byte Duplicate ID 0 => 302
2014-02-13 04:01 Dark Byte Status new => resolved
2014-02-13 04:01 Dark Byte Resolution open => fixed
2014-02-13 04:01 Dark Byte Assigned To => Dark Byte
+Issue History