Use Tables! » SoC http://www.gijsk.com/blog Except not really. Mon, 28 Jun 2010 09:33:32 +0000 en hourly 1 http://wordpress.org/?v=3.0 Domain name and SoC results http://www.gijsk.com/blog/2006/08/domain-name-and-soc-results/ http://www.gijsk.com/blog/2006/08/domain-name-and-soc-results/#comments Mon, 21 Aug 2006 08:10:54 +0000 Gijs http://www.gijsk.com/blog/2006/08/domain-name-and-soc-results/ So, first stop: I finally got and pointed the domain name www.gijsk.com to this site. WordPress has been updated to that effect, or so I think, and hopefully all you people’s DNS servers will be, too, within a few hours/days.

Seconds stop: I’ve published a convenience page with my patches and some handy-dandy xpi files. You might find it interesting, or so I hope :-) .

Now I’m off to go packing and do some last-minute shopping for my holiday. I just checked in (and picked perfect seats) from my desk chair – SAS are great so far!

]]> http://www.gijsk.com/blog/2006/08/domain-name-and-soc-results/feed/ 1 Robbed, hiatus http://www.gijsk.com/blog/2006/08/robbed-hiatus/ http://www.gijsk.com/blog/2006/08/robbed-hiatus/#comments Fri, 18 Aug 2006 09:57:19 +0000 Gijs http://gijs.codingo.org/blog/2006/08/robbed-hiatus/ Yesterday someone rang my doorbell, asked if I wanted to buy dvd’s from him, and upon my negative answer forced the door open wider (I’d only put it ajar) and pointed a knife at me. Me being unarmed and not much of a fighter, I didn’t do much but trying to stay calm, and he eventually left with my digital camera, an mp3 player and 40 euro in cash (but not my wallet (bank cards, creditcard…) or my laptop (which had been hiding under an empty shopping bag, by pure chance)).

Obviously I called the cops later on, and spent much of yesterday recounting the story to various people, roughly half of them police officers. I didn’t sleep much tonight, and I’m taking a break for two days to calm down and such… James Ross found a small Venkman bug that I want to squash on sunday if I feel more normal psychologically. In the meantime I’m at my parents. Mail will reach me.

]]> http://www.gijsk.com/blog/2006/08/robbed-hiatus/feed/ 4 Stuff gets marked FIXED http://www.gijsk.com/blog/2006/08/stuff-gets-marked-fixed/ http://www.gijsk.com/blog/2006/08/stuff-gets-marked-fixed/#comments Wed, 09 Aug 2006 23:53:48 +0000 Gijs http://gijs.codingo.org/blog/2006/08/stuff-gets-marked-fixed/ Task List

And I’m happy. But it doesn’t end here, I still want to fix 2 more things on that list, and obviously I need to get all those patches reviewed and checked in. After which, right now, things look as if I’ll end up with 2/3 of my original list finished (the security issues popped up during the whole thing, and in the end turned out to be out of my league for the most part), and 3/4 of it resolved (1 worksforme, 1 wontfix). Additionally, it’s the top 15 items, so that hopefully means I’ll have stuck to my priorities pretty well.
I hope people feel that’s enough (for now), and we’ll see how things work out, won’t we? :-)

On a separate note, I’ll be going on a holiday to Sweden the early morning of August 22 (yes, that’s the day after the deadline). Speaking of deadline, I have a little counter on my home pc that I’ll try to hack into this wordpress thing. By the time you read this is it should hopefully be there. :-)

]]> http://www.gijsk.com/blog/2006/08/stuff-gets-marked-fixed/feed/ 0 Back http://www.gijsk.com/blog/2006/07/back/ http://www.gijsk.com/blog/2006/07/back/#comments Tue, 18 Jul 2006 09:34:09 +0000 Gijs http://gijs.codingo.org/blog/2006/07/back/ I’m back from my away time. I still have to get into a good daily rhythm after so much time in what’s really a different world, I suppose, but I’ll be alright within the coming week. I’ve caught up with email and such, just need to start being productive again. :-)

]]> http://www.gijsk.com/blog/2006/07/back/feed/ 0 Vacation http://www.gijsk.com/blog/2006/07/vacation/ http://www.gijsk.com/blog/2006/07/vacation/#comments Sat, 08 Jul 2006 20:41:57 +0000 Gijs http://gijs.codingo.org/blog/2006/07/vacation/ As of tomorrow morning 4am I’m on holiday, vacation or sabbatical if you prefer that word. I’ll be off to France and will be without internet access in the coming week. I will return on July 16, and you can expect me to start replying to email (and generally being alive in the ‘net sense of things) again on July 17. If you need me for Summer of Code or Mozilla stuff, you can send me email and I’ll get back to you ASAP on July 16 or 17.

]]> http://www.gijsk.com/blog/2006/07/vacation/feed/ 0 Debugging from the dialog of death (2) http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death-2/ http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death-2/#comments Sat, 24 Jun 2006 16:11:32 +0000 Gijs http://gijs.codingo.org/blog/2006/06/debugging-from-the-dialog-of-death-2/ bug 341764 is now fixed on both trunk and the 1.8 branch, meaning you can now debug from the slow script warning dialog if you have a debugger like Firebug or Venkman open. Woo! :-)

]]> http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death-2/feed/ 0 Debugging from the Dialog of Death http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death/ http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death/#comments Mon, 19 Jun 2006 09:00:17 +0000 Gijs http://gijs.codingo.org/blog/2006/06/debugging-from-the-dialog-of-death/ On the title: The Dialog of death just sounds so much better than the “Slow Script warning”. Regardless, if a developer encounters a dialog like it unexpectedly, it generally means they screwed up. Unfortunately, right now they can’t in any way check why that happened. If they stop the script, then that’s just that and they have no way of going back into the slow state. If they choose to continue running the script they won’t get anywhere either because usually in cases like that all other UI is hung.

Solution? Add a debug script button to the dialog if and only if there’s an active debugger open. The debugger can be Firebug or Venkman, but it should work just as well if an external debugger is in use (like the ATF one that you get when developing XUL stuff in Eclipse). There’s a patch for branch and for trunk on bug 341764, but I would definitely prefer if this solution only ended up on branch (permanently), given that creating an optional dependency in DOM on JSD seems not that right (in this case optional means that DOM will still build fine without JSD (–disable-jsd) and will just use it if it can).

So now the waiting is for the review people to notice my requests and hopefully have time soon. :-)

technorati tags:, , , , , , , ,

]]> http://www.gijsk.com/blog/2006/06/debugging-from-the-dialog-of-death/feed/ 0 Profiling Venkman / JSD startup http://www.gijsk.com/blog/2006/06/profiling-venkman-jsd-startup/ http://www.gijsk.com/blog/2006/06/profiling-venkman-jsd-startup/#comments Sun, 04 Jun 2006 16:40:59 +0000 Gijs http://gijs.codingo.org/blog/2006/06/profiling-venkman-jsd-startup/ So the last few days I’ve been trying to get a profile of Venkman/JSD startup. First I’ll talk about the hurdles I met along the way for a bit. I decided that the results and conclusions I took from them are probably better off on a wiki page. Please feel free to let me know what you think about them.

Problems and stuff

First of all, I wanted to do a profile on my Windows box, because it’s faster than anything else I have access to, and I really wanted this to not be a task taking me more than a few hours, maybe a day. Wrong plan. There are no open-source/free profile tools that I could find (documentation/explanations of). On Linux, there was more choice, and several people told me that was probably easier for me. Okay, I thought, then we’ll have to do it on Linux, I guess. Not very nice, but oh well.

Surprise surprise, there is documentation! I’ll probably move that to DevMo/wiki.m.o if desired, and if/when I have spare time. So, off I went, trying to build with the following .mozconfig:

# Options for client.mk.
mk_add_options MOZ_CO_PROJECT=suite,browser,mail,xulrunner
mk_add_options MOZ_OBJDIR=/home/gijs/moz_dev/firefox-opt-jprof/
mk_add_options MOZ_MAKE_FLAGS="-s -j4"

# Options for 'configure' (same as command-line options).
ac_add_options --enable-application=browser
ac_add_options --enable-debugger-info-modules
ac_add_options --enable-optimize
ac_add_options --disable-debug
ac_add_options --enable-jprof

The first hurdle was that jprof required bfd.h. My build failed, I apt-got binutils-dev, and then that part of the build was happy again – except that it then started to complain that _r_debug was not defined. After some lxr-ing, I wondered what was up, because this seemed to be something that should get from some external thing (meaning, a header or library or other ‘thing’ not provided by mozilla itself), yet neither make nor ld was complaining about missing headers. When complaining in #developers, biesi fortunately heard me and told me to put EXTRA_DSO_LDOPTS += /lib/ld-linux.so.2 in the Makefile.in for the directory that was failing (mozilla/tools/jprof/stub). After that, the build worked fine.

That said, it was very slow. In the meantime, I’d used some spare unpartitioned space on my main Windows machine to install Ubuntu Dapper. The laptop was running Ubuntu Breezy, and after the build was done, I updated that machine to Dapper as well. After that I tried to profile my build which seemed, not counting some hurdles with which dbaron helped me, to work fine. However, when I ran jprof on the resulting jprof-log file, it complained it couldn’t find a library file. Oops. I now (after the OS update) had a different version of that library, rendering the build mostly useless (at least, that’s my diagnostic of what happened – I didn’t look into it too much, maybe I’m wrong and something else was broken, I don’t know). Regardless, I rm -fr‘d my OBJDIR, and started the build anew.

By now I had overcome some entirely unrelated problems with Ubuntu Dapper on my main machine, and after some time, noticing how slow the build on my laptop was, I started a cvs checkout on my main machine. After installing cvs, that is (why is that not in a default Dapper install – and why did Dapper not let me pick the software I wanted when I was installing in Expert mode?). Then I did a checkout (after installing make, anyway), and meanwhile used apt-get to install gcc, g++, libidl and all the other prerequisites to do anything useful with a cvs checkout.

When my checkout was done, I ran a build, then realized I’d forgotten to separately checkout jprof and edit the Makefile to make sure I wouldn’t get the same problem. I did those things while the build was already running, and surprisingly that worked. My main machine was done before the laptop (I partially blame my addition of --disable-tests to the .mozconfig on my main machine for that extremely large difference).
I then ran a profile on my main machine (in a nutshell, I set the environment variable JPROF_FLAGS to “JP_DEFER JP_PERIOD=0.0011″, ran Firefox, sent it a PROF signal, started Venkman, sent Firefox a USR1 signal as soon as Venkman was done loading, and then exited Firefox (and Venkman)). After checking the results, I was suspicious for the lack of jsd stuff in there. I then realized this profile still had Firebug installed, which I suspected would get its debugger interface sorted out as soon as the first Firefox window got loaded. So I deinstalled Firebug and tried again. The next day (today) I did the same thing on my laptop. The results are on wiki.mozilla.org.

]]> http://www.gijsk.com/blog/2006/06/profiling-venkman-jsd-startup/feed/ 0 </barcamp><soc alt="spending time on mozilla"> http://www.gijsk.com/blog/2006/05/barcamp-end-soc-start/ http://www.gijsk.com/blog/2006/05/barcamp-end-soc-start/#comments Wed, 24 May 2006 09:51:04 +0000 Gijs http://gijs.codingo.org/blog/2006/05/barcamp-end-soc-start/ So, 3 days after barcamp ended, Google gave me official word that I’ve been accepted in the Google Summer of Code. I will be working to improve the JS Debugging experience in Mozilla Firefox, specifically for webdevelopers. In order to do so, I need input from the (other) people who debug their own javascript on a daily basis.

  • What’s missing?
  • What’s been done wrong? What’s been done exceptionally right?
  • What tools do you use? Why?
  • Do you use Venkman? Why, or why not?
  • Do you use the MS Script debugger? Why, why not?
  • Is either tool better than the other, and if so, why?
  • What kind of problems do you spend the largest amount of time on, and how can a debugger help you change that (or at least shorten that amount of time)?

You can email me a response to those questions, but you can also comment on the tracking bug for my project, or on this blogpost. Thanks in advance!

]]> http://www.gijsk.com/blog/2006/05/barcamp-end-soc-start/feed/ 0