Cheat Engine Forum Index Cheat Engine
The Official Site of Cheat Engine
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 


Possible Bugs

 
Post new topic   Reply to topic    Cheat Engine Forum Index -> Cheat Engine
View previous topic :: View next topic  
Author Message
MRDB512
Advanced Cheater
Reputation: 0

Joined: 31 Aug 2007
Posts: 60

PostPosted: Thu Sep 11, 2008 10:17 am    Post subject: Possible Bugs Reply with quote

Update:
Possible Bug - Was also going to post the save code, always saves all opcodes and fields regardless of option selected.
But...
http://forum.cheatengine.org/viewtopic.php?t=289729

Update:
I tried to make my own [disable] code
and to write value 0 by to register instead of just replacing code with original

the user can't alloc Newmem
There should be an exception for this in the [disable] tab

In the [Disable] tab in AA Scripting...
for example
The user can't make there own [disable] code!
please Check and Fix!.
There is no check for the [disable] code to use the same alloc name i.e newmem
Cos the code [enable] writes to code cave and then I would like
[disable] write to the same code cave, cos once [disable] tab is active then the code cave on, [enable], is useless, until [enable] tab is active.
and when [enable] tab is active, it writes to the same code cave anyway
so the opcodes the [disable] tab wrote. would be overwritten.

So, thats fine. backwards compatible.

Possible Bug - Cant use the alloc function in [disable] tab in AA scripting...
Please Check and Fix


Thanks,
==================================

Update:
Do a Find out what Accesses or Read or Writes to this address
and Go into Memory Viewer, Break And Trace = Error = Ok fine.

but here is were the possible bug is, go back and Click |Stop|
go back into Memory Viewer, now Try break and Trace = Error

Point is, user should not have to close the window. |stop| Should be all thats needed

Please Check and Comment!
------------------------------



-----------------------------------------
TprgressBar - out of range

I Saved more then, 3 times the same data,
or different data
it pauses, and then stalls!
-----------------------------------------------------------------------
Auto Assembler
[Template], with option one and then option four
= no [disable] data written!
Reverse the order, so four and then one,
theres no check = error the code get jumbled

------------------------------------------------------------------------
Try to Save, Any code in Auto Assembler from the Memory Viewer
Either Starting with or containing = Error

Code like: Float point and Stacks
Fadd
Fsub
Fmul
or stacks:

st(0)

or the two conbined!
fadd st(0)

Cant work with stacks = error,

=======================
Summery of possible bugs:

Needed to Click |stop| and Then Close to Break and Trace in memory viewer.

Save Disassembled output,
TProgressbar out of range

Auto Assembler
Framework, option one with option four
no [disable] code written

Framework, option four with option one,

no check, and code just jumbled

Memory Viewer,
Try to Auto Assemble,

Code Movcx or movsx
Code St(0) or
most Stack Code and Float point Code

e.g.
anycode with fadd st(0) in it or fadd st(2),will not allow you to enter in AA Script //error!
Fadd
Fsub
Fmul


Please Check


Please Let me know if the above our Bugs

_________________
DATABASE

Its a good learn trip, but at the end you would want to know
how you got there!


Last edited by MRDB512 on Thu Sep 18, 2008 6:52 pm; edited 5 times in total
Back to top
View user's profile Send private message
Dark Byte
Site Admin
Reputation: 470

Joined: 09 May 2003
Posts: 25804
Location: The netherlands

PostPosted: Thu Sep 11, 2008 12:15 pm    Post subject: Reply with quote

try splitting these up into separate reports and add them to the bug tracker on the site

anyhow,
save disassembled output: confirmed (didn't get the progressbar error, but I did notice it didn't properly cleanup)
edit: fixed in svn

auto assembler template: Not really a bug, the enable/disable is just to put a enable in front and end at the back for people that are too lazy.
The enable part doesn't always have to be the same as the disable. (e.g in situation where once hooked it can never go back)
But I have changed the part where you do the code injection part after enable/disable

st(0) problem, confirmed, it's a disassembler bug for leaving out the st(0) part
temp bypass:
fadd st(0),st(0)
edit: fixed in svn

_________________
Do not ask me about online cheats. I don't know any and wont help finding them.

Like my help? Join me on Patreon so i can keep helping
Back to top
View user's profile Send private message MSN Messenger
Display posts from previous:   
Post new topic   Reply to topic    Cheat Engine Forum Index -> Cheat Engine All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group

CE Wiki   IRC (#CEF)   Twitter
Third party websites