Forum Home
Press F1
 
Thread ID: 33606 2003-05-20 23:00:00 PressF1 problems - Status Biggles (121) Press F1
Post ID Timestamp Content User
146004 2003-05-20 23:00:00 Just so you all know we are working on fixing these crashes. The guys are currently logging what is going on to try and establish exactly what the fault is. Really sorry for the ongoing inconvenience. Biggles (121)
146005 2003-05-21 01:34:00 Isallright Bruce. Murray P (44)
146006 2003-05-21 02:03:00 I am prepared to wait as we are lucky to have such a site for fun..education.....technology know how...ranting and raving and I hope SO SAY ALL OF US? olldaddy76 (2539)
146007 2003-05-21 04:58:00 In My case your hopes are fulfilled. Thomas (1820)
146008 2003-05-21 05:31:00 Speaking of that, could someone explain to me what a NullPointerException error actually is? (or whatever it is?)... I see people pointing the finger of PF1 faults at it, but I don't know what it really is or what "NullPointers" have to do with PF1's errors...

Thanks



CyberChuck
cyberchuck (173)
146009 2003-05-21 05:58:00 pointers are a programming thing.

null is meaning nothing.

you have a pointer and it tells the program where to look for the bit of data. a null pointer is not set to point to anything and so when you go and have a look the program crashes or something bad like that.

where do null pointer come from?

when you make a new bit of data (a post on the forum) the program make a new pointer (which is set to null by ths OS) and then tells the OS I ahve this data to stor where can i put it? the OS will return a pointer to a place for the program to store the info.

the problem come when the program stores the data but dosent the pale in the pointer. this means that the pointer is still set to null and when it goes back to get the data it cant find it and "throws" a null pointer error.

hope that makes sence.


as for fixing this problem, it could be anywhere in 10000 lines of code :-)
robsonde (120)
146010 2003-05-21 06:04:00 and a version with less mistakes :-0




pointers are a programming thing .

null is meaning nothing .

you have a pointer and it tells the program where to
look for the bit of data . a null pointer is not set
to point to anything and so when you go and have a
look the program crashes or something bad like that .

where do null pointer come from?

when you make a new bit of data (a post on the forum)
the program makes a new pointer (which is set to null
by ths OS) and then tells the OS I have this data to
store where can i put it? the OS will return a location value
to a place for the program to store the info .

the problem come when the program stores the data but
dosent store the location value in the pointer . this means that the
pointer is still set to null and when it goes back to
get the data it cant find it and "throws" a null
pointer error .

hope that makes sence .


as for fixing this problem, it could be anywhere in 10000 lines of code :-)

look I cant find the mistakes in 30 lines of posting!!
robsonde (120)
146011 2003-05-21 06:57:00 Thanks for that :D cyberchuck (173)
146012 2003-05-21 07:01:00 "Curently logging" . Gee, considering all of the resources that pressf1 have on hand I would have thought logging would have been tried months ago .

And yeah I know it's for free and we can't expect too much, nevertheless I would have thought we would have been down this road before now .

Well anyway . . . Good luck in trapping the little bugger .
Tobas (224)
146013 2003-05-21 07:11:00 ...So I hear that its not you this time Bruce?

;-)

You guys will get it nailed...

Look, if you get stuck, I know of this website you can goto.. its mainly end-user to end-user help.. Great Forum.. Hmm, only thing is they've been having a bit of trouble lately...

;-)
Chilling_Silently (228)
1 2 3 4 5 6 7 8