Jump to content

Heap overflow


Punct.

Recommended Posts

Care-i treaba cu erorile din consola cu Head overflow? De la ce apar si cum se poate evita aparita lor?

[debug] Run time error 8: "Heap underflow"
[debug]  Heap pointer (HEA) is 0x0, heap bottom (HLW) is 0x85B390
[debug] AMX backtrace:
[debug] Run time error 8: "Heap underflow"
[debug]  Heap pointer (HEA) is 0x0, heap bottom (HLW) is 0x85B390
[debug] AMX backtrace:

 

Am citit cate ceva pe .com, dar nu ma descurc prea bine la enleza si nu am inteles mare lucru.

Nu mai deschideti in pu*a mea servere de SA:MP !

Jucati-va pe cele care sunt !   Sunt suficiente !

Reguli de bun simt:

1. Nu faceti reclama unde nu trebuie !

2. Nu injurati ca la usa cortului !

3. Daca esti analfabeti, taci din gura !

4. Nu abuza de 'scuze', 'din greseala' !

 

My work ::: http://pastebin.com/VRNRcaAs

Link to comment
Share on other sites

pawno.exe

 

Am un pus #pragma dynamic 500000, si nu mai apar, dar vreau sa stiu si ce e asta si de la ce provine.

Nu mai deschideti in pu*a mea servere de SA:MP !

Jucati-va pe cele care sunt !   Sunt suficiente !

Reguli de bun simt:

1. Nu faceti reclama unde nu trebuie !

2. Nu injurati ca la usa cortului !

3. Daca esti analfabeti, taci din gura !

4. Nu abuza de 'scuze', 'din greseala' !

 

My work ::: http://pastebin.com/VRNRcaAs

Link to comment
Share on other sites

Stivele si Heap sunt pe RAM adica cantitatea de memorie si locatia acesteia in memoria RAM, aceste erori apar cand nu gaseste suficient spatiu pentru a se desfasura, la compilare normal isi aloca aceste valori! Daca declari local un array mare, de ordinul miilor, cand o sa executi un for cu acest numar de pasi, ai toate sansele sa nu reuseasca.

Citeste mai multe despre memorarea stivelor si despre Heap.

Link to comment
Share on other sites

Inseama ca folosesti multa memorie in HEAP.

Poate sa fie cauzata de la vectori mari, dar trebuie sa gasesti unde este problema. 

Uite ce zice Y_Less

This means that the compiler has detected that you are using more stack/heap space than is available. A lot of important information is stored on the stack, such as who called the current function, so PAWN knows where to return to. If you use too much memory, because of the way information is allocated, you can overwrite the stack information, returning to a random point in code and almost certainly crashing. At the very least you will get corrupted data where it's been overwritten by other data. When people get this message the standard advice is to use "#pragma dynamic", which is a workaround, not a fix - I find it very odd that something the size of YSI can not generate this error but people's tiny scripts can, don't you?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more details you can also review our Terms of Use and Privacy Policy.