As a seasoned C++ developer I should’ve been aware of this which makes it a little bit embarrassing. But, since this issue has cost me several hours of searching through the Internet over the course of two or three days, I thought it might be worth sharing. Maybe somebody else is trying to be too smart or just doesn’t know better.
The problem? It is summarized in short in this StackOverflow question that I posted. With this blog post I’ll be a bit more elaborate and show some details.
Read More »
Grails always has something new to offer, not only features but also random bugs (unfortunately). Out of the blue I couldn’t even let Grails show its own version (grails –version) let alone perform any other action. This is all I got for each and every command I tried to execute.
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message transform method call failed at
../../../src/share/instrument/JPLISAgent.c line: 844
Exception: java.lang.StackOverflowError thrown from the
UncaughtExceptionHandler in thread "main"
The following runtimes were used:
- Windows 7 64bit
- Java 7 Update 71 64bit
- Grails 2.4.4
Of course I removed all temporary files and folders, the “target” folder of the project and the “.grails”, “.groovy”, “.m2” and “.ivy” folders in the user directory. Nothing helped. Some say it has to do with forking processes, but playing with those settings didn’t change a thing. After all, the error happens way earlier.
Then I came across a post that mentioned to create the “.inputrc” file (on a Linux system) because through debugging it was found that Grails tries to access this files. Well, I’m not using Linux, but since I was already in the “helplessly desperate” phase I wanted to give it a shot. Surprisingly, this file already existed.
Solution: I deleted “.inputrc” from the user folder et voilà, Grails worked again.
Recently I wanted to install a Gigabyte Radeon HD7870 in an older PC with an ASRock P67 Pro3 Mainboard. The surprise was big when the monitor didn’t show an image and the computer didn’t boot. Instead, the mainboard’s debug panel showed the error code 97. According to the manual this means “Console Output devices connect”. Not connectED but more likely in the process of initializing the graphics card and failing while doing that.
There’s an easy fix for that. Installing the latest BIOS version (3.30, installed at the time was 2.02) resolved the issue and the computer booted without problems.
Recently I have updated our Grails 2.3 based web application to Grails 2.4. Although the 2.3 release was working fine, one doesn’t want to fall too far behind. I know out of experience that this can happen very fast. If you wait too long, then at some point the migration to a newer version is almost like starting from scratch, instead of just updating a few lines of code to accommodate for deprecated APIs. The biggest problem I encountered going to version 2.4 was a behavioral change regarding the validation.
Read More »
When building the PC for gaming on the TV one thing I had in mind was leveraging the already existing 5.1 sound system. After the move from the TV screen back to a desktop monitor I thought my headphones would suffice for the time spent playing games. At first that assumption turned out to be true, however, not only did I use the headphones for gaming but also when watching TV shows. In the evening, after work, I wanted to enjoy the audio but had no interest in disturbing my neighbors. After a while this led to the headphones becoming quite uncomfortable for all those hours wearing them, especially during the weekend gaming session when having them on the head for several hours.
So, what does a tech-nerd do about that? Buy himself a dedicated sound system for the PC, he does!
Read More »