Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug memory overflows gdb.exe #23

Closed
IamLupo opened this issue Sep 20, 2014 · 5 comments
Closed

Debug memory overflows gdb.exe #23

IamLupo opened this issue Sep 20, 2014 · 5 comments

Comments

@IamLupo
Copy link

IamLupo commented Sep 20, 2014

When I debug in SAsM my assembler code and I debug a memory variable thats in this case array size 100000. It will increase gdb.exe memory every time a instuction runs. Eventually gdb.exe crashes.
When i debug in SASM and don't debug memory i don't have this issue.

@Dman95
Copy link
Owner

Dman95 commented Sep 20, 2014

Can you give me the source code of the program that causes crashes?

@IamLupo
Copy link
Author

IamLupo commented Sep 21, 2014

I used the SASM 3.1.0 Version.
Source Code: http://pastebin.com/mJRbPQFZ

At first i put a break on every instruction, second i put the ptr_data in the memory debug and put in the size 10000000. When i run the instructions by pressing f5. The gdb.exe is increasing in memory in taskmanager every time i run a instruction. If i run enough instructions gdb.exe crashes.

@Dman95
Copy link
Owner

Dman95 commented Sep 21, 2014

Internally SASM perform "print (int[10000000]) *((int *)ptr_data)" command to watch array variable ptr_data. Debugging in GDB without SASM causes same crash. It seems that an error in GDB.

@Dman95 Dman95 closed this as completed Sep 21, 2014
@Dman95
Copy link
Owner

Dman95 commented Sep 21, 2014

To avoid this bug you can watch array variable by parts. All the same you can not watch on 10000000 values at once.

@Dman95 Dman95 reopened this Sep 21, 2014
@Dman95 Dman95 closed this as completed Sep 21, 2014
@IamLupo
Copy link
Author

IamLupo commented Sep 21, 2014

Oke, i already had a feeling this could be a bug in gdb. But very thx to take a look at it ^_^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants