![]() |
Bug-NUM_FOR_EDICT Error: Bad Pointer
Sup all.
Thought I would start a new thread on this bug since I have now gotten this error typicaly on map change. Have not really pin pointed which maps are doing it yet. Please if anyone else is getting this error and has some code to post to fix this that would be great. Again, only post code on this bug on this thread. Thanx :D Lastly, could anyone who posts code post it in a way so anyone can understand it at to where the fix needs to be changed. Thanx to all that contribute. Until next time..Cheers! |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Asurmen, yes I know of this bug but.. I have no idea what that error means or what could be causing it because I have never experienced it.
Could you give some steps to reproduce it somehow? make sure you can reproduce it a few times. I'll be checking in the code where the server changes maps. and what command did you use to change the map? "changelevel"/"map" and also post some information about your setup. and does this only happen in 1.6? |
Update...
Spiorygon,
My setup is: Steam CS 1.6 Listen Server Metamod 1.17X3 from AMXX site-which seems to not matter which one I use wether it is the Filebase on this site or the above. Latest Podbot MM here at Bots-United AMXX 0.16 I do not use AMX anymore since the last update from Valve basicly made it un-usable. I have done quite of testing with several bots in the past. I just haven't done much debugging. Is there any commands that I can add to my shorcut and or listenserver.cfg to get the information that would shed light on this? Thanx. Until next time...Cheers! |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
I get this bug now as well on my dedicated mEAn PODbot server. The maps I experience this on are de_nuke , and as_oilrig. In the past I had this bug when I first started working on getting POD up and running on a 1.6 listen server. The error at that time would occur the instant the bomb was to drop out of the hand to the ground. I fixed this problem by reinstalling metamod, podbot, and amx. Anyway I haven't spent alot of time figuring out why its happening now, I know it doesn't happen on the map change. There is deffinately an action that triggers this kind of error. Wether its a sound that gets asked for or what I'm not sure.
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Well the way I'm interpreting this error is...
There was a BAD Pointer (pointed to some wrong memory address) that was supposed to be pointed at an edict (entity). |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
I think what your looking for can be found in the quake 1 source...
Code:
int NUM_FOR_EDICT(edict_t *e) |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Well I was in the middle of a massive cs_office bot pwnage and it poped up :(
Well now I know it happens in 1.5 also. I still don't know what is causing it because mine wasn't during changelevel but it did change round using amx's voting. |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
A friend of mine is running CS 1.6 on a Linux DS (just MM + PB), and he gets the error, too. Also on cs_office, among other maps I don't remember right now. So it really seems to be on all platforms, CS versions and OS'es... :(
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Perhaps it happens only on a certain type of maps ?
for example cs_ maps ? That would be a problem related to hostages... |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Asurmen, try to delete all *.pxp and all *.pvi files from your WPTDEFAULT directory. After this test once again and describe us step by step, what did You do to see crash?
For example 1. I start to play on map de_dust. 2. Timelimit for map has reached. 3. New map cs_italy has began to load. 4. I saw the crash with this NUM_FOR_EDICT. Write us , what is a date stamp of pwf file corresponding to map at which CS crashed. For example if You saw the crash at cs_office, write us date and time of creating the file cs_office.pwf in WPTDEFAULT directory. |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
no no hostages coz it happens on de_ maps too..it's the bots...
maybe the easiest way is to play 1v1 bots...and wait n watch the bots for the crash.. it may take a while but if it happens and u see the bot tha did it then maybe..we could home in on the prob... or u could just demo the enitire games which would be easier i guess... |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
you can't get a demo..
cuz when it crashes the demo file will be corrupt... |
Update-Bug-NUM_FOR_EDICT Error: Bad Pointer
Sup all. Back again with an Update.
I have done some testing and found out the problem at least on my machine. THe latest PODBot MM works just fine if I don't load AMX or AMXX mod. This is as of the most recent Steam update. I'm loadig metamod from the lblist.gam file and I'm loading AMXX from the plugins.ini along with the podbot_mm.dll. This error seems to not be with metamod or podbot, but with AMXX mod and or AMX because as soon as I put back in the amxx_mm.dll in the plugins.ini I start getting the NUM_FOR_EDICT Error: Bad Pointer error. Also. that is does not happen at map change it will happen right in the middle of action and or game play. That's what I have say so far. Until next time...Cheers! |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Well, lucky guy if leaving out AMX fixed the problem for you. On my PC, I recently got one bad pointer error (the first one I had seen, but I don't run mapcyles, only occasional mapchanges when I'm testing waypoints, that's why), and I don't even have AMX.
My friend Robert also reported this error, and he doesn't have AMX or any other mods except for MM and the bot itself installed, either. :( |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Well I have done some things to try and fix this so lets hope it is fixed...
I can't test if it is fixed or not since I've only gotten this error once and have not been able to get it again... I've made a lot of changes to the bot too.. Just waiting for some people to respond and hopefully it'll be out today. |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
That's good news. As soon as it's out, I'll send it over to Robert so he can test it on his Linux DS - he had this error pretty often, so if he says he doesn't see it anymore I guess we can pretend it's fixed for good. :)
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
as far as i know itz a problem with the bot...as one said mostly happens in intensene action ... so it's a problem with bot combat or movement.....i'm thinking something with combat....
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Yes i also get this error Bad Pointer
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
well I have now added...
Code:
int pfnIndexOfEdict (const edict_t *pEdict) [edit] btw, PMB whats going on? still checking it out? [/edit] |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Yes I am. Sorry, I've been away the whole weekend. But I've just got your 2 PMs and I've downloaded the bot.
Hold on 2 seconds... :) |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Quote:
calling ENTINDEX() or INDEXENT() in the bot plugin won't get here... |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Quote:
on the good side... I didn't know INDEXENT could cause it too :D I was only checking ENTINDEX :D [edit] another good news might be that I might have found where it is being caused... and it does have something to do with intense battles.. at least the dying part... in BotClient.cpp I changed this: Code:
void BotClient_CS_DeathMsg (void *p, int bot_index) Code:
void BotClient_CS_DeathMsg (void *p, int bot_index) [/edit |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
If you changed this in the latest version of PODbot i am still getting this error to let you know
[EDIT] My bad i didn't read before i typed thanks for updating PODbot Splorygon |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
so you used R2.1 and still getting the error?
if so... I SERIOUSLY do NOT know what is wrong.. I've checked every SINGLE call to INDEXENT and ENTINDEX... They all have a check to make sure that it's not null... We will probably have to wait for Austin to come help debug this... |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
yeah i am still getting the error after like 2 rounds
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Only thing i can think of is if theres another way to cause this error besides giving a null ent to INDEXENT or ENTINDEX....
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Hey wow i just though about this i relized that everytime CS encounters an error it makes an error log. this is the error log it creates everytime it does the NUM_FOR_EDICT
Error:Failed to load dialog file Resource/UI/ClassMenu.res Function trace: CGameUI::Start CGameUI::Initialize CBaseUI::Start CBaseUI::Initialize Host_Init CFileSystem_Steam::Mount() Thats it i hope it helps |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
are you sure thats the log to the correct error?
that looks like a steam error... well anyways any info can be useful... as long as it's in the right direction.. but I don't know what to do with that info.. |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
thats steam error ..happens without bots too in normal play.....
this error is definatley coz of the bot move or combat when an intense battle happens....i've been playing with them (2.1) for a while with no error...(good :) )i think we need printf fuctions to trace this bug... too bad it's one of those that haapen once in a while :( (for me at least) |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Yes well i suspected it was it i tested it to make sure i had like 5 of these logs so i played CS again and let it crash and then i had 6 logs so i assumse that was the problem
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
I also thought there was a problem when you are trying to get the ent pointer from index 0. I thought you had to start from 1 till gpGLobals->maxclients...
so try and find any for loop which starts at 0.. Well, i can't bet on it. But i remembered in some cases it goes wrong here. Another thing could be you have a <= instead of a <... I am not sure, but perhaps its 0 till 31 instead of 1 till 32 you can figure this out yourself to be sure, gtg. |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
i have been testing podbots versions for a long time now
and i have noticed this problem form time to time few notes 1. more bots means more probable the error will occur - i have tested that 20 botts will crash serverr very fast 2. it may be something with dying and maybe item dropping 3. i'm not sure if it is possible but i have noticed fw times that server crashed when i was under fire and was sure i gonna die :P and then seeing the bot that aimed at me was jumping gonna make more detailed checks if you need i hope the notices will not be misleading, so just think of them and not use them for 100% one more thing - with the latest official release of podbot 2.6mm from ehre (that is around 2004-04-28 ) the bot crashes really much rarely also i was wondering if some optimization methohds during compiling can have dramatic effect on this (like -02 or other switches that sometimes are not good) i'm testing podbot on amd k6-II 500 on cs 1.6 linux box with amx the bot crashes even if running pure hlds without plugins (except metamod) |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
if you notice this error
Error:Failed to load dialog file Resource/UI/ClassMenu.res Function trace: CGameUI::Start CGameUI::Initialize CBaseUI::Start CBaseUI::Initialize Host_Init CFileSystem_Steam::Mount() it is trying to load a file "ClassMenu.res" which apparently doesn't exsist i don't know if this has a bearing on it but i hope it helps |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
as i said b4 it's a steam error and has nothing to do with bot's if u check the steam forums ....most ppl get that error and there's no proper fix for it...
and it doesn't really affect the game play n stuffs |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
true but why do i get this error log everytime CS crashes with the NUM_FOR_EDICT Error
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
i'm not sure but i think it get generated at any hl.exe crash as i haven't had many crashes of "NUM_FOR_EDICT Error: Bad Pointer" yet i got plenty of error logs of that steam classres error
i think u'll have to system.out.print....umm c++ alternative to that to find out whats going on.....it'z a long way to go that way but it'z the best way... |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
okay i've did a few changes and I'd like for the people who get this error a lot to test it...
http://www.mapzap.org/files/podbot/podbotBETA.zip |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
nope still getting the error
|
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
Then there really must be something else that can cause that error that I don't know about...
[edit] finally been able to crash... I seems to only get it on cs_office... I've tried de_dust, awp_map, as_oilrig, cs_office, and cs_assault so far... but only cs_office has crashed... leaving me with log files. http://www.mapzap.org/L0512006.log.txt http://www.mapzap.org/L0512007.log.txt both happened on cs_office they still don't help me much :( [/edit] |
Re: Bug-NUM_FOR_EDICT Error: Bad Pointer
i got crashes on any map :/
one more thing first i was using hlds with default binary, that is hlds_486 but i got amd k6-II cpu in the result the hlds was freezing very often - not crash but freezed. then i started to expeoriment with binary hlds_amd not only the hlds works now much smoother but the bots are crashing the hlds and not freesing i got crashes very very rarely now - myabe once on few map changes, but always... i am using the podbot recompiled on my own machine with the fixes for the 'unnamed' bots, using gcc 2.95.3 |
All times are GMT +2. The time now is 07:37. |
Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.