[Programming] Tools to detect buffer overflow
Moderator: BigEvilCorporation
[Programming] Tools to detect buffer overflow
I'm working on my genesis emulator and i start to implement the sound part.
Since this part is terminated i have randomly crash and i'm sure is because buffer overflow occuring.
Does anyone know if exist tools to detect where there is data writing outside the alloctaed area?
I'm working with code::block and gcc compiler.
Thanks for your help !
Since this part is terminated i have randomly crash and i'm sure is because buffer overflow occuring.
Does anyone know if exist tools to detect where there is data writing outside the alloctaed area?
I'm working with code::block and gcc compiler.
Thanks for your help !
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
Another useful one is STrace to really get into the meat of your Function calls.mickagame wrote:My emulator is cross-plateform so it wouldn't be difficult to developp it under linux.
I will try it because i'm curious t osee how it run on linux plateform.
=> Dr Memory help me to find the function where i was doing buffer overflow.
Now all is perfect
UNIX also has plenty of Tools to debug Shared-Memory Segments and such - I feel sorry for anyone who has to develop for Windows
UMDK Fanboy
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
UNIX generally has most it not all of the Tools. Historically many of the Tool and OS advancements arrived on UNIX first. The other thing is that good Tools are not lost between OSes and OS version so the same Tool that you used twenty years ago will still be there.
I had a guy working with me years ago who had not used VI the Editor for 17 years and he was straight back into using it without any issues as things worked and his knowledge was still valid.
UNIX respects knowledge and you will find that anything you learn can be relied up on.
I suppose that's why I love UNIX
I had a guy working with me years ago who had not used VI the Editor for 17 years and he was straight back into using it without any issues as things worked and his knowledge was still valid.
UNIX respects knowledge and you will find that anything you learn can be relied up on.
I suppose that's why I love UNIX
UMDK Fanboy