2017-09-24 21:55 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000372Cheat Engine(No Category)public2015-02-10 22:21
Reporterpausebreak7 
Assigned ToDark Byte 
PriorityhighSeveritycrashReproducibilityalways
StatusresolvedResolutionno change required 
Summary0000372: DarkByte Cheat engine Dbvm bsod crash bug?
DescriptionMy linux dbvm 64bit compile 369kb(377 856byte)
Cheat Engine Rev 2902 Run

DBVM Version 8 Load -> Process Open -> Find Out What Accesses this address click
->Computer Bsod Crash ShutDown


TagsNo tags attached.
Attached Files

-Relationships
+Relationships

-Notes

~0000744

pausebreak7 (reporter)

Compile make clean cdimage

vmdisk144.img and vmdisk.img Copy Cheat engine Folder
dbk64.sys
cheatengine-x86_64.exe
vmdisk.img and vmdisk144.img

Do I need any other files?

----------------------------------
vmdisk.img 285KB (291,840 byte) <--Cheat engine 6.4 Original Release vmdisk.img

Not Bsod

my vmdisk.img 369kb(377 856byte) <--Bsod

~0000745

pausebreak7 (reporter)

computer info:
cpu: i5 Sandy Bridge
ram: 16GB
hdd: ssd
vga: NVIDIA GTX

~0000746

pausebreak7 (reporter)

my linux ubuntu 14.04 Compile

How do I use a different compiler?

I would like to know your build environment

~0000747

Dark Byte (developer)

i used linux mint 14 and compile it using "make clean install"
but are you sure it's your build being the culprit? It could be it's the 30% chance you crash. Does it always crash? And does it crash when starting it from the about screen?

it's possible you need an older version of gcc. I read somewhere that it has changed the calling convention recently(16 byte alignment of the stack, including 32 bit code)

~0000748

pausebreak7 (reporter)

The compiled file size is too different

You think there is a problem with the compilation method?

But Cheat engine Source Error?

~0000749

pausebreak7 (reporter)

Always crash 100%

~0000750

Dark Byte (developer)

Last edited: 2015-02-10 17:33

View 3 revisions

https://code.google.com/p/cheat-engine/source/browse/trunk/dbvm/vmm/common.h
comment line 6 and 7 (or if you have a serial port adjust the makefile, it will help with debugging)
perhaps 11 as well

edit: actually, just edit https://code.google.com/p/cheat-engine/source/browse/trunk/dbvm/Makefile
and set serialport to 0

~0000751

pausebreak7 (reporter)

Dark Byte

serial port to 0 compile bsod not crash

Why do you do that?

~0000752

Dark Byte (developer)

when serialport is not 0 it compiles into debug mode
in debug mode right before it starts, it prints out a menu with lots of options to the serial port, and then waits for the user to send it an option. (e. g. 0 to start)
but if no one is sending it the command to start, it will wait forever

~0000753

pausebreak7 (reporter)

Dark Byte Thank you^^

Have a nice day!
+Notes

-Issue History
Date Modified Username Field Change
2015-02-10 15:09 pausebreak7 New Issue
2015-02-10 15:09 pausebreak7 File Added: error bsod.png
2015-02-10 16:29 pausebreak7 Note Added: 0000744
2015-02-10 16:47 pausebreak7 Note Added: 0000745
2015-02-10 17:05 pausebreak7 Note Added: 0000746
2015-02-10 17:23 Dark Byte Note Added: 0000747
2015-02-10 17:24 pausebreak7 Note Added: 0000748
2015-02-10 17:27 pausebreak7 Note Added: 0000749
2015-02-10 17:29 Dark Byte Note Added: 0000750
2015-02-10 17:30 Dark Byte Note Edited: 0000750 View Revisions
2015-02-10 17:33 Dark Byte Note Edited: 0000750 View Revisions
2015-02-10 17:47 pausebreak7 Note Added: 0000751
2015-02-10 18:05 Dark Byte Note Added: 0000752
2015-02-10 18:11 pausebreak7 Note Added: 0000753
2015-02-10 22:21 Dark Byte Status new => resolved
2015-02-10 22:21 Dark Byte Resolution open => no change required
2015-02-10 22:21 Dark Byte Assigned To => Dark Byte
+Issue History