Sometimes when you are developing you encounter the stranged errors. Today is just such a day. I’m right now having issues with memory access violations in on of the programs I’m developing.
This on its own is not that big of a deal, but I can’t seem to trace down why it’s happening. If I debug the function that causes the error has no issues. No memory violations, but when I continue running (without debugging every single call) then all of a sudden at some point in time I get a memory access violation.
Now I don’t exactly know where it’s comming from. It may have something to do with the fact that the object I’m deleting is a prototype of a prototype. And also occasionally gives me an error during compile time that I have no destructor in the class. But when I compile the files one by one it does not give this error. And the class in question does have a default destructor.
Hmm, guess it’s time for some real line by line debugging and digging into the internet about the obscure error message I got.
Below are some of the pictures taken during my brief 2 week vacation in the Autumn break 2008.
You might have noticed it yesterday, or not ;). But my blog and several other websites hosted by me went offline yesterday for a couple of hours. Well this had to do with me upgrading the VPS to Debian Etch.
So far I ran every website on Debian Sarge, and though it’s stable they choose to no longer developer for it nor support it. So it was time to move to a newer version. Wich I did yesterday. Here’s some of the steps you should take before upgrading to the next version of Debian.
I was lucky that my hosting provider offers an easy way to upgrade or reinstall a Linux distro on the VPS. Just a couple of mouse clicks and they prepare the VPS for the installation. Please note that this will take up to an hour to complete. Once this base installation is complete you will want to perform the following steps:
From this point on your ready to go. All of the websites should be running without any problems. You do need to configure any other tools you had installed, like AWStats / Subversion or anything else. Though these should not require to much configuration as all of the configuration files where included in your backup. At least if you followed a setup similar to my first article on setting up linux.
After my first post on upgrading the HTC P3300 (Dopod P800 in the US) some time back it’s time for yet another post on this, see ‘Windows Mobile 6 on HTC P3300′.
This time round I’ve been playing around with two seperate versions of custom ROMs for the HTC P3300. The first one I’ve looked at is the ‘Black&Blue 5.0′ ROM, written by Tom. The second one is the ‘Oops Black 1.0′ also written by Tom. If you need information on how to install these ROMs then look at my earlier article and follow those steps, except you don’t install the Windows Mobile 6.0 ROM but one of the two below.
The main reason for me to use this ROM was that it was build on top of Windows Mobile 6.1. Why was this so important you may think. Well let me list a couple of nice new features in:
Though it’s not a big list the first one was reason enough for me. Finally a Windows Mobile version that I don’t need a styles to operate. Some of the parts I really liked about this ROM was that it was really fast. And even better really stable. I’ve had no problems what so ever using this ROM.
You can download the ROM Black&Blue 5.0 here.
Like I stated before the second ROM I tested was a relatively new one written by Tom. The base of this ROM is identical to the Black&Blue one. It’s also running on Windows Mobile 6.1 and has more or less the same applications installed. One huge difference is that this ROM is attempting to emulate the Touch Diamond style.
For those of you interested in this please let me give you a warning in advance. The ROM looks a lot like the Touch Diamond, but it’s behaviour is nothing like it. So if you are interested in the eye-candy this ROM is for you. If you want the functionality behind it then buy the new phone.
You can download the Oops Black 1.0 here.
Warning notice: Please note that both of these ROMs have been written by a 3rd party, which means you’r phone operator will not support you if your phone breaks. As to support from HTC they might, but you did modify the phone without approval.
Ok a very short follow up on my previous Netbeans 6.5 impression. Previously I stated that I had some serious problems with the debugging. It failed to indicate which line I was on.
After some research and some more debugging this only appears to happen when debugging jsp files or jspf files. For a beta that is something I can live with. Beyond that the debugger works like a charm.
I did however found some other issues:
To be fair I have to say I never got Netbeans itself to crash. But you do get an exception window that asks you to file a bug report.