Fernando Meyer

Are you tired to run ant scripts and wait for tests results whenever you change some source file? Yes, me too, basically I got autotest’s idea for ruby and Did it work for ant as well. Continually runs tests based on files you’ve changed improving feedback with a fancy Growl alert.

If you are a Java developer and works with ant (on mac of course) check out my bash script( and avoid cruise control for little stuf ) **see update

Change all images paths on the script, put the script in your project folder and execute it

remember you need unit tests to use this script properly.


If you have some idea on how to improve it, let me know

** now hosted at github

git clone git://github.com/fmeyer/autotestmac.git

I just updated my MBP to the latest Apple’s OS 10 ( leopard ) the system is good, few eye-candies updates, although was a bit disappointing don’t see java6 around ( they removed the early beta version from ADC as well, so, don’t waste your time looking for it).

Apple, I don’t care about java6 for now you can delay it until you make it good. BUT… man when you delivery something with your OperatingSystem make sure that this thing works, I got really angry with a BUGGED java5 version, the exactly version is

java version “1.5.0_13″
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

This bug looks like its deep inside Apple’s windowing toolkit implementation as you can see in the following stack trace

Exception in thread “AWT-EventQueue-0″ java.lang.NullPointerException
at apple.awt.CGraphicsEnvironment.displayChanged(CGraphicsEnvironment.java:65)
Invalid memory access of location 00000000 eip=00000000
at apple.awt.CToolkit$4.run(CToolkit.java:1259)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.j

ava:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java

A guy from GWT dev list submitted a bug report to Apple: Problem ID 5563333 - “CGraphicsEnvironment NullPointerException breaks continually on OsX 10.5″, so engineers and QA move your asses and get this thing done, because you are affecting my work and some more guys around the world.

When launching Google web toolkit you get this error, org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError?: mozilla-1.7.12/libxpcom.so: Can’t load IA 32-bit .so on a IA 32-bit platform)

FC6 has libstdc++.so.6.0.8 out of the box. Many times yum is smart enough to get the “compat” version of a lib when a newer one is installed, so I rolled the dice and tried:

yum install libstdc++.so.5

When launching the Eclipse debugger you get this error,
ERROR: transport error 202: gethostbyname: unknown host “transport.c”,L41?
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) “debugInit.c”,L500?

To correct the problem, just add the following line to /etc/hosts :

127.0.0.1 localhost

Probably it will be useful for you, as was for me.

I don’t know why but it’s happening, every time when i open a second gmail tab my Firefox crashes

Exception: EXC_BAD_INSTRUCTION (0×0002)
Code[0]: 0×0000000d
Code[1]: 0×00006e64

Thread 0 Crashed:
0   libSystem.B.dylib                  0×90029ae5 _longjmp + 37
1   <<00000000>>     0xc00101dd 0 + -1073675811

I was looking for some similar bug at firefox bugzilla but, I didn’t found anything about it. That isn’t the unique problem, I’m coding a web interface to access and test some Webservices, then I discovered another bug: div element with visibility:hidden still show scrollbars, I couldn’t reproduce the problem on Firefox running over Win32 with the same html file, so I think that’s a bug.

What if a debugger could allow you to simply step BACKWARDS? Instead of all that hassle with guessing where to put breakpoints and the fear of typing “continue” one too many times… What if you could simply go backwards to see what went wrong? This is the essence of the “Omniscient Debugger” — it remembers everything that happened during the run of a program, and allows the programmer to “step backwards in time” to see what happened at any point of the program. All variable values, all objects, all method calls, all exceptions are recorded and the programmer can now look at anything that happened at any time

HomePage: http://www.lambdacs.com/debugger/debugger.html

Article: http://www.lambdacs.com/debugger/Article.html

Video: http://video.google.com/videoplay?docid=3897010229726822034&q=engedu+debugging