[06:25] <lilstevie> is anyone about?
[09:23] <lag> ogra: Ping
[09:41] <hrw> morgen
[09:46] <lag> hrw: Morning
[09:46] <lag> hrw: Thanks for the Linked-in add
[09:46] <hrw> np
[09:46] <lag> hrw: You'd do well to change your picture
[09:46] <lag> :)
[09:46] <lag> You don't look like that anymore :)
[09:47] <hrw> I am lazy when it comes to pictures
[09:49] <lag> It's the reason I didn't recognise you in Prague
[09:49] <hrw> I shaved and haircut on Thursday
[09:50] <lag> Did you have hair before then?
[09:52] <hrw> yep
[09:52] <lag> A big change for you then
[09:52] <lag> It looks better now
[10:19] <lag> mythripk: ping
[11:00] <XorA> heh makes ubuntu sound like a cult, must shave head before meeting :-)
[11:02] <lag> Well you know that computer programmers have a reputation for being intimidating and hard! ;)
[11:04]  * XorA wonders if Henry Rollins is an ubuntu developer
[11:06] <lag> I hear Charles Bronson also dabbles
[11:17] <hrw> I wrote nice patch during sprint - it dropped hrw@ubuntu.com from binutils/README.cross as such one does not exists
[11:17]  * hrw is neither Debian or Ubuntu developer
[11:18] <lool> Would someone know which host is the armel porter box in the Canonical DC?
[11:18] <lool> I tried rimu and jocote, but these are dead apparently
[11:37] <lag> lool: kakadu
[11:45] <lool> lag: kakadu to you too
[11:45] <lool> oh wait, is that an hostname?   :)
[11:45] <lag> lool: Yes :)
[11:46] <lool> lag: Works, thanks
[11:47] <lag> lool: np
[11:48] <lool> lag: Do you know how to install build-deps?
[11:48] <lool> hmm apt-get install
[11:49] <lag> lool: What are you trying to do?
[11:49] <lool> lag: install build-deps of a package; sudo apt-get install works
[11:49] <lool> ERROR: package 'libjack0' marked for removal but the system does not allow removals
[11:49] <lool> hmpf
[11:51] <lag> :)
[11:51] <lag> Nothing to do with me
[11:51] <lag> You'll have to speak to IS
[11:51] <lool> it's ok, I can live without the package I was missing; it seems it will meed mvo to fix some rapt script
[11:51] <lool> first time I see this script BTW
[11:54] <lool> chrisccoulson: Hey
[11:55] <chrisccoulson> hi!
[11:55] <lool> chrisccoulson: Unfortunately, yao is .cn and michaelh .nz, and they are both offline now
[11:55] <chrisccoulson> ah, ok
[11:55] <lool> (they are the main folks looking into the issue, and the other folks have other tasks)
[11:56] <chrisccoulson> i'm just trying to figure out how to run it without jit (i know it's possible to do that when creating the JSContext, but i'm not sure if it looks for something in the environment)
[11:57] <hrw> lool: apt-get build-dep package
[11:57] <lool> hrw: this doesnt work in the porter boxes
[11:57] <lool> hrw: only apt-get install is allowed
[11:57] <hrw> ok, good to know
[11:57]  * hrw avoids foreign machines
[11:59] <lool> chrisccoulson: Running it on imacro_asm.js alone is enough to crash it, but on an empty file or on imacros.jsasm, it doesn't crash
[11:59] <ukleinek> lool: apt-get install -o "Dir::Etc::SourceList $HOME/mysources.list" setuidbash :-)
[11:59] <chrisccoulson> lool, yeah, i'm seeing the same behaviour here
[11:59] <lool> ukleinek: Eh
[12:03] <lool> chrisccoulson: A trivial file with "i = 0;"
[12:03] <lool> breaks it
[12:04] <chrisccoulson> lool - i think it's already running without JIT (in any case, running with "-j" still causes it to crash, and that option toggles the state of JIT)
[12:05] <lool> chrisccoulson: Hmm ok, there's also a -o jit, but I couldn't unset it properly
[12:05] <lool> chrisccoulson: Would it make sense to try to build the tip of the js tree from mozilla-central to see if it's still there?
[12:06] <chrisccoulson> i just had a look at the code for the shell, and passing "-j" causes it to do "JS_ToggleOptions(cx, JSOPTION_JIT);"
[12:06] <lool> chrisccoulson: a workaround we could try is -fno-strict-aliasing
[12:07] <lool> chrisccoulson: lunch here, bbl
[12:38]  * lag wonders where ogra is today
[12:38] <ogra> busy with non IRC stuff, sorry
[12:38] <ogra> whats up ?
[12:39] <lag> np
[12:39] <lag> The daily builds appear to have stopped building on the 20th?
[12:40] <ogra> yes, there are issues with the image size of the filesystem
[12:40] <ogra> i'm working on debugging it
[12:40] <lool> chrisccoulson: back
[12:40] <lag> ogra: And the 20th is the one that's broken
[12:40] <ogra> somehow we create to small images for no apparent reasons
[12:41] <ogra> so the cp'ing of the chroot content fails with "no space left on device" errors
[12:41] <lag> Is this something you're working on right now?
[12:41] <ogra> yes
[12:41] <lag> Then I'll leave you to it
[12:41] <ogra> i dont get the reason though
[12:41] <lag> Can you poke me when it's complete
[12:41] <ogra> df -ks |cut -f1 is how we get the size
[12:42] <lag> df: invalid option -- 's'
[12:42] <lag> Try `df --help' for more information.
[12:42] <ogra> dd if=/dev/zero of=<image> bs=1024 count=0 seek=<size> ... is how we create the image
[12:42] <ogra> err
[12:42] <ogra> du -ks, sorry
[12:42] <lag> Okay, that works
[12:42] <ogra> according to the manpage du -ks gives me the value of 1k bytes
[12:43] <ogra> so using bs=1024 needs to create an exactly sized image file
[12:44] <ogra> i dont get where the overhead comes from
[12:44] <ogra> apparently there is some
[12:44] <chrisccoulson> lool - i was just about to try building our firefox-4.0 package, which is basically what's in mozilla-central;
[12:44] <lool> ogra: what do you du?
[12:44] <lag> ogra: Yes it does
[12:44] <ogra> lool, creating ext2 images
[12:44] <lool> chrisccoulson: Ok, I copied over src/js and ran autoconf, configure, and am building now
[12:44] <lool> chrisccoulson: But your plan sounds good
[12:45] <ukleinek> ogra: there is some fs overhead, no?
[12:45] <lool> ogra: Do you du the .img file, or the contents of the image?
[12:45] <ogra> lool, the build chroot
[12:45] <lool> even if you du all files in the fs, there is more space used by the fs
[12:45] <lool> with fs structures
[12:45] <lool> superblocks for instance are obviously not accounted per file
[12:45] <ogra> we also add 10M for a potential journal to the size variable
[12:46] <ogra> yeah
[12:46] <ogra> i would have expected to have some overhead, but more than 10 meg ?
[12:46] <lool> this seems really fragile
[12:47] <ogra> it is what livecd-roofs uses for the squashfs size computation
[12:47] <ogra> seems ext*fs has some more overhead
[12:47] <ogra> (the same code is used by angstrom for creating their images btw)
[12:48] <ukleinek> ogra: apt-cache show genext2fs
[12:48] <ogra> ukleinek, thats what causes my headdache
[12:49] <ogra> and why i'm working at the code :)
[12:49] <ukleinek> ah, I thought there was no need to specify an image-size
[12:49] <lool> chrisccoulson: Happy to hear when you have a firefox-4.0 build finished; if my tip build doesn't help, I'll try with -fno-strict-aliasing
[12:49] <ogra> genext2fs allocates the whole size of the target image in ram
[12:49] <ogra> before copying anything into it
[12:50] <ogra> with our 1.6G images that takes 2h and about 2G swap
[12:50] <ukleinek> huh
[12:50] <ogra> we initially used genext2fs ... i'm currently attempting to switch to a loop mounted img file instead
[12:52] <lool> loop-mounted?  doesn't that require root?
[12:53] <ogra> lool, we have root on the livefs builders
[12:54] <ogra> no prob there
[12:54] <ogra> just not on antimony
[12:54] <lool> oh right
[12:54] <ogra> 21032 blocks (5.00%) reserved for the super user
[12:54] <ogra> heh
[12:54] <ogra> silly me :P
[13:08] <lool> chrisccoulson: js from mozilla-central segfaults too
[13:09] <chrisccoulson> lool - ah, ok. i can probably stop the firefox-4 build then
[13:12] <lool> chrisccoulson: Hmm it doesn't use any shared libs or anything does it?
[13:12] <lool> chrisccoulson: I'm running gdb on the unstripped shell/js file, but the stacktrace is worthless, did you do anything to get a nice backtrace?
[13:12] <lool> Reading symbols from /home/lool/js/src/shell/js...(no debugging symbols found)...done.
[13:12] <lool> uh
[13:12] <lool> ah, not built with -g *me bangs head*
[13:13] <chrisccoulson> heh ;)
[13:13]  * lool builds with -g -ggdb -O0 -fno-strict-aliasing now
[13:13] <lool> chrisccoulson: ~lool/js/src.tgz is a base tree ifyou like
[13:14]  * lool grmpfs - mozilla configure doesn't take CFLAGS on the cmdline
[13:18] <hrw> ~curse linux-meta ubuntu crap
[13:19] <hrw> apt-get source linux-what-it-is-called-today suxx
[13:21] <amitk> hrw: it is always linux-image-<flavour>
[13:21] <hrw> no,  it is linux-image-version-abi-flavour
[13:22] <hrw> and version and abi changes daily, twice daily, weekly, randomly
[13:22] <amitk> I thought you wanted meta source?
[13:22] <hrw> no
[13:22] <hrw> I want source
[13:22] <amitk> sure, whats wrong with abi changing?
[13:22] <hrw> if I want meta I do 'apt-get source linux-meta'
[13:22] <ogra> apt-get source linux ?
[13:22] <hrw> ogra: will grab linux-meta instead
[13:22] <ogra> oh, right
[13:22]  * ogra always forgets that
[13:23] <hrw> ogra: there was bug about it since ubuntu 3.04 or older
[13:23] <hrw> bug #-2
[13:23] <lool> hrw: apt-get --only-source source linux
[13:24] <hrw> lool: thx
[13:31] <lool> crap, I have to pass CXXFLAGS as well
[13:33] <lool> There, finally, it builds with the proper flags
[13:35] <dyfet> ogra: hi!  I have not had a chance to unpack yet
[13:36] <ogra> dyfet, take your time
[13:36] <dyfet> well, I also have some pain killers for my eye...
[13:47] <lool> GRR -O3 overrides my user-specified -O0
[13:48] <lool> and -fstrict-aliasing as well
[13:48] <lool> chrisccoulson: How is one expected to pass flags to the builds?
[13:48] <chrisccoulson> lool, what flags do you want to pass?
[13:49] <lool> chrisccoulson: I'd like to pass CFLAGS="-g -ggdb -O0 -fno-strict-aliasing -Wall" CXXFLAGS="$CFLAGS"
[13:49] <lool> MODULE_OPTIMIZE_FLAGS is apparently what I'm supposed to set
[13:49] <lool> and INTERP_OPTIMIZER, sigh
[13:50] <chrisccoulson> lool - doing "export CFLAGS=...." before running configure should work
[13:50] <lool> chrisccoulson: does not, MODULE_OPTIMIZE_FLAGS and INTERP_OPTIMIZER take precedence (my flags are passed, but overriden later in command-lines)
[13:51] <lool> I see some -Os now, from /somewhere/
[13:52] <lool> chrisccoulson: The evil thing is that different files are compiled with different opts, so it seemed like I was finally using the proper ones, but no, I wasn't for some files   :-/
[13:52] <chrisccoulson> lool - does it work if you build with --disable-optimize?
[13:53] <lool> chrisccoulson: Didn't try that one
[13:53] <lool> MOZ_OPTIMIZE_FLAGS is where -Os comes from
[13:53] <chrisccoulson> --disable-optimize should switch off building different files with different optimizations
[13:54] <lool> I will pass that *and* turn all the nasty flags off explicitly on make
[13:59]  * lool looks hard and doesn't see any -Os or -O3 or -fstrict-aliasing anymore
[13:59] <lool> and the build is faster in -O0
[14:06] <lool> chrisccoulson: Yep, same issue with every opt turned off
[14:07] <lool> same bt
[14:07] <lool> #0  0x00072688 in js_CheckForStringIndex (id=1514652) at jsobj.cpp:4006
[14:07] <lool> #1  0x00073c9c in js_SetPropertyHelper (cx=0x1b7900, obj=0x40602000,  id=1514652, defineHow=9, vp=0xbeb433c0) at jsobj.cpp:5012
[14:07] <asac> lool: if you want to use the same -Ox everywhere you can say: --enable-optmize="-Os"  for instance ... this will override all subtree optimization etc. (not sure if thats what you ask)
[14:08] <lool> asac: that was the goal, yes, well that and other flags
[14:09] <asac> lool: the subtree optimizes are tuned by mozilla. they would be happy to get better tuning for armel from talking to a few folks at moz summit. but just -O2 etc. wont be right.
[14:09] <asac> what problem triggers this?
[14:09] <asac> crashes with our new toolchain?
[14:10] <lool> chrisccoulson: eh, s == 0x00000008 now
[14:11] <lool> asac: the js interpreter in xulrunner/firefox builds is broken with the new toolchain
[14:11] <lool> asac: What I hate with the mozilla thing is that my flags don't get precedence
[14:11] <asac> kk
[14:12] <asac> which flags do you want to remove/add?
[14:12] <asac> lool: ?
[14:13] <lool> asac: it's ok now, the flags were discussed earlier here: -O0, -g, -ggdb, -Wall, -fno-strict-aliasing and such
[14:13] <asac> k
[14:13] <lool> I managed to pass the flags, but now I'm trying to debug, and it doesn't look too nice
[14:13] <asac> lool: for best debugging you could use --disable-optimize and --enable-debug
[14:14] <asac> and then start it from dist/bin directly
[14:14] <asac> (but i guess that was already mentioned too)
[14:19] <lool> asac: This is the information I was looking for earlier, but now I have a debug build
[14:19] <lool> asac: Are you tempted to look into this?
[14:21] <asac> lool: --enable-debug also enables assertion logging etc. so it might be helpful if you dont get that atm. (e.g. if you start you should see a bunch of prints etc.)
[14:22] <asac> lool: i dont think i will be able figure these toolchain induced problems easily.
[14:39] <hrw> zumbi: thx for mail - will reply
[14:39] <rsalveti> morning
[14:40] <zumbi> hrw: no problem.. I do not know why i did not see it before
[14:46] <hrw> zumbi: number of your ITP is?
[14:48] <zumbi> hrw: why?
[14:50] <zumbi> 553682
[14:50] <zumbi> 553683
[14:50] <zumbi> 553684
[14:50] <zumbi> 553685
[14:50] <zumbi> 553687
[14:51] <zumbi> and discussion upon -devel
[14:52] <lool> zumbi: So what's the model for these sources?
[14:53] <lool> zumbi: Is it the same source tree uploaded multiple times?
[14:53] <lool> gcc-4.3, does someone still care about this??
[14:53] <lool> zumbi: what about linux headers?
[14:54] <zumbi> 553679
[14:55] <hrw> zumbi: wanted to read
[14:56] <lool> hrw: read?
[14:56] <hrw> lool: yes, read - I do such thing with bug reports
[14:57] <lool> zumbi: So I see only one gcc and one eglibc source package; I understand you will go through 6 or so uploads at least everytime the linux headers change or something
[14:57] <zumbi> lool: i prefer delay discussion for debconf
[14:57] <lool> zumbi: Your ITPs seem to use the same model I was using for my cross-toolchain source tree, is that the one?
[14:57] <hrw> zumbi: bookmarked those
[14:58] <hrw> zumbi: will mail debian-embedded/linaro-toolchain with more info
[14:58] <zumbi> lool: not exactly, but i keep you in copyright files
[14:58] <zumbi> hrw: thanks
[14:59] <lool> zumbi: I personally concluded that this wasn't a sane model
[14:59] <lool> Too many uploads, or out of date toolchains, and too many source packages
[15:00] <zumbi> lool: is not your model, and what do you care? I am the one who step up for maintainance
[15:00] <zumbi> within Debian
[15:00] <zumbi> I have been holding upload for later discussion
[15:00] <zumbi> multiarch, sysroot and emdebian way of doing things
[15:00] <lool> zumbi: I care because I will be using Debian cross-toolchains too, and because I care about Debian!
[15:01] <zumbi> I would prefer to coordinate with you all, so I propose to discuss this at debconf
[15:01] <lool> zumbi: Discussing at Debconf is fine too, but we can as well discuss some of it now?
[15:01] <zumbi> please note I am not against you
[15:01] <lool> One doesn't prevent the other  :)
[15:01] <hrw> zumbi: now we have "source binary packages" for eglibc, gcc-4.[45], linux, binutils
[15:01] <lool> zumbi: I'm not saying you're against me
[15:01] <zumbi> lool: I am at work
[15:02] <zumbi> none pais me to do this work
[15:02] <lool> zumbi: Ok; if you can't chat now, we can chat later or only at debconf
[15:02] <hrw> zumbi: soon (before maverick alpha3 if all go ok) we will have stages support in eglibc/gcc/linux and also their debian/rules* in *-source packages
[15:02] <zumbi> later should be fine, but i rather have a meeting at debconf if you really care (on all arches)
[15:02] <lool> zumbi: I don't think the arches matter really
[15:02] <zumbi> hrw: but only working on armel :/
[15:03] <hrw> zumbi: no - any non-bi/triarch
[15:03] <lool> zumbi: It's unfortunate that we broke other arches, but it's not intended and am sure it can be fixes
[15:03] <lool> *fixed
[15:03] <hrw> zumbi: tested only for armel yes
[15:04] <zumbi> hey guys, lets better discuss later or by mail if you do not mind
[15:04] <hrw> sure
[15:04] <zumbi> please, and I am not against you
[15:04] <rsavoye> does maverick-ARM run under QEMU at all ?
[15:04] <hrw> I hope that we (Linaro and Emdebian) will have a chance once to meet in one place and discuss
[15:04] <hrw> rsavoye: should
[15:05] <rsavoye> is it faster than a beagle ? :-)
[15:05] <hrw> zumbi: I am trying to be as much as possible not against anyone. If I will became such then tell
[15:05] <hrw> rsavoye: maybe on 30GHz x86-64...
[15:05] <hrw> that zero is not mistake
[15:06] <rsavoye> oh well...
[15:06] <zumbi> hrw: no, you are fine
[15:06] <rsavoye> too bad cross-compiling is so broken for most packages
[15:07] <hrw> rsavoye: thats debian/ubuntu errors
[15:07] <zumbi> hrw: but i have the feeling that lool, slangasek and partialy doko, do not undetrstand me and they are somehow mad at me. But it is just a feeling.
[15:07] <XorA> hrw has the patches to fix thousands of cross compile issues :-)
[15:07] <hrw> rsavoye: openembedded has thousands of cross compiled ones
[15:07] <rsavoye> I know, but I prefer to not use the OE build style
[15:08] <hrw> zumbi: they did less crosscompilations that we did
[15:08] <lool> zumbi: I'm not mad at you  :-)
[15:08] <slangasek> zumbi: I'm not mad at you, but you clearly working at cross-purposes to what we're trying to achieve with multiarch
[15:08] <hrw> rsavoye: so merge our (OE) patches
[15:08] <rsavoye> unfortunately it was OpenJDK I was hoping to cross compile, but it looks like a mess
[15:08] <lool> zumbi: You seem to be pushing for solutions which we identified as incomplete already
[15:08] <hrw> rsavoye: it is a mess but crossbuildable mess
[15:08] <slangasek> and I've already explained how this is the case, so I'm at a loss to how I can clarify this
[15:08] <zumbi> slangasek: happy to hear that I hope we can discuss further at debconf
[15:09] <hrw> so far I am ignoring 'multiarch' word and just do cross stuff
[15:09] <rsavoye> I see the long list of patches, I have to decide if I want to apply them all, and then fix things to cross compile with your toolchain, not OE
[15:09] <hrw> rsavoye: I know
[15:10] <zumbi> lool: I am not pushing anything, I could have the upload done and end with the issue. But I hold because I want consensus. Let's better talk at debconf and please also consider Squeeze release in mind
[15:10] <zumbi> hrw: how does OE build their cross toolchains? do they use sysroot?
[15:10] <zumbi> hrw: have you experienced the with-libs/with-headers pain?
[15:11] <hrw> zumbi: sysroot only now
[15:11] <hrw> zumbi: non sysroot way is argh but I feel that multiarch debian will force that way
[15:12] <zumbi> yes, everybody does, I do not know why do not work for lool
[15:12] <zumbi> anyway, lets better delay discussion for later (or debconf)
[15:13] <hrw> I hope for notes from debconf meeting
[15:14] <zumbi> hrw: I always try to be transparent -- do not worry for that
[15:15] <lool> zumbi: Well if you had proceeded with an upload, you wouldn't have put an end to the issue, since I would be unhappy  :-)
[15:16] <lool> zumbi: There are multiple discussions going on; one is about cross-compiler packages, and another one is about cross-compiling Debian
[15:16] <lool> Concerning cross-compiler packages, what you used to do should still be possible in the future, but might be temporarily broken (patches welcome); it should also be more solid going forward
[15:16] <lool> Since we don't have parallel sets of rules for cross versus non-cross
[15:17] <lool> It will *also* allow uploading a single cross-toolchain-armel package which will trigger a while toolchain bootstrap
[15:17] <lool> You don't seem to look at the latter, I don't understand why
[15:17] <slangasek> zumbi: to satisfy the requirements for multiarch, the trees for all architectures *must* have the same root, and it must be /; and consequently, sysroot will fail to allow coinstallability, because the architecture tuple is part of the sysroot path, *not* part of the paths for the subdirectories
[15:17] <zumbi> I rather have binutils-cross which builds all binutils targets
[15:17] <lool> I went with the 4 source packages + 6 uploads route myself, just like the one you ITP-ed, and it's *pain*, and we have another way which seems superior?
[15:18] <hrw> zumbi: 'all binutils targets' == all arches?
[15:18] <lool> zumbi: This is a valid approach, it's not what you ITP-ed; I don't think it's a good approach either, but for different reasons
[15:18] <lool> hrw: *That's what I understood at least)
[15:19] <zumbi> slangasek: yes, at the end, I understand your point :) -- but I am still convinced that multiarch and sysroot should be compatible and that is not going to happen for Squeeze, later we can change
[15:19] <slangasek> I don't see any reason they wouldn't be compatible
[15:20] <slangasek> it's just that neither helps the goals of the other
[15:20] <zumbi> lool: sure, ITP should be renamed then, I though on that after filing the ITP, but that time none care, so I did not had to coordinate much
[15:21] <zumbi> slangasek: true, I saw your point, makes sense to me
[15:22] <lool> zumbi: I don't think having multiarch and sysroot compatible wouldn't land for squeeze, it's not a complex patch, just need to agree on pathnames
[15:25] <zumbi> lool: sure, lets talk later or at debconf about it. And let me repeat, I am not against you, but I was the only one caring on cross tools on the last 5-6 years, and doko does not even allow me to touch his tree.
[15:25] <zumbi> but hey.. does not matter! We are good friends and we can discuss this like persons
[15:27]  * ogra GRRs at the archive 
[15:32] <lool> zumbi: I'm not against you, I'm against the proposal of -armel packages because I went through that and I think that's heavy, and I'm against the proposal of -cross packages because I think that's ugly, but we can talk this over   :-)
[15:33] <zumbi> lool: sure - I am open for discussion :)
[15:34] <zumbi> lool: indeed, that was doko plan, he wanted only armel in the archive, but there are other devels that would like to have any-to-any arch, like we had on lenny
[15:35] <lool> zumbi: I would like to allow amy-to-any, but I'm not sure the Debian archive is the best place for this
[15:35] <lool> In Ubuntu, I understand only cross-armel will be provided
[15:35] <ogra> now who is amy ?
[15:35] <lool> on i386 and amd64
[16:36] <lag> robclark: ping
[16:36] <robclark> lag: pong
[16:37] <lag> robclark: Can you explain to me in simple terms what a lost-digit is please?
[16:37] <robclark> lag: basically I think it means that sync is lost..  although I'm not yet sure why it happens over and over a gazillion times
[16:39] <lag> Oh, you see that too?
[16:39] <lag> I thought it was just me and my weird monitor
[16:43] <lag> robclark: ?
[16:43] <robclark> lag: yeah..
[16:43] <robclark> (sorry, multitasking)
[16:44] <lag> Mythri's patch fixes this issue for me
[16:44] <robclark> yeah, I'm still cleaning up my patch, and then I need to rebase on mythripk's latest
[16:44] <robclark> I'm hoping that helps
[17:07] <hrw> ~curse libelf<>libelfg
[18:19] <chrisccoulson> lool - i'm not sure whether you noticed this already, but the jsid is getting mangled between frames 1 and 2 of https://pastebin.canonical.com/35036/
[18:20] <chrisccoulson> #1  0x2a043c86 in js_DefineNativeProperty (cx=0x2a0d6b80, obj=0x2a0f80c0,
[18:20] <chrisccoulson>     id=705479548, value=22, getter=0x2a03f695 <block_getProperty>,
[18:20] <chrisccoulson>     setter=0x2a03f631 <block_setProperty>, attrs=69, flags=4, shortid=0,
[18:20] <chrisccoulson>     propp=0x0, defineHow=0)
[18:20] <chrisccoulson> #2  0x2a0440a2 in js_DefineBlockVariable (cx=0x2a0cc37c, obj=0x2a0cc378,
[18:20] <chrisccoulson>     id=705523208, index=<value optimized out>)
[18:20] <chrisccoulson> the id parameters should be the same
[18:25] <chrisccoulson> in fact, all of the arguments passed to js_DefineNativeProperty are wrong
[18:26] <XorA> bah lucid x86 dual boot broken :-(
[18:27] <lool> chrisccoulson: Oh
[18:27] <lool> chrisccoulson: that's very interesting
[19:37] <jayabharath> all - Where can I find daily build images for OMAP4/ubuntu?
[19:45] <rsalveti> jayabharath: http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current
[19:46] <rsalveti> there you can find the omap 3 and omap 4 images
[19:47] <rsalveti> jayabharath: http://testcases.qa.ubuntu.com/Install/ARM/PreinstalledImage if you need instructions to install it
[19:54] <jayabharath> rsalveti: thanks. Do these images work on OMAP4 Blaze platform?
[19:55] <rsalveti> GrueMaster: did you ever test this image on blaze?
[19:55] <rsalveti> jayabharath: I'm not sure, but I believe it should work
[19:56] <rsalveti> I just tested/saw it on a normal panda
[19:56] <GrueMaster> rsalveti: I don't have a blaze (yet).
[19:56] <jayabharath> I see... ogra should have it (my guess)
[19:56] <jayabharath> anyway will check it out and go from there
[19:57] <rsalveti> jayabharath: yeah, let us know if it worked or not
[19:57] <jayabharath> ok
[21:15] <Henk___> Hallo word de arm-wm8505 ondersteunt
[21:33] <Neko> boo
[21:58] <mpoirier> davidm ?
[23:10] <cwillu_at_work> segfaults in system-config-printer when poking at a windows network
[23:22] <pcacjr> cwillu_at_work: please, report the bug
[23:23] <cwillu_at_work> pcacjr, seems to be dups around, I'm still reading through them, and being distracted by other folks :p
[23:23] <pcacjr> cwillu_at_work, oh, i see. heh :-)
[23:37] <cwillu_at_work> pcacjr, https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/370293 looks pretty similar
[23:37] <ubot2`> Ubuntu bug 370293 in nss-mdns (Ubuntu) "system-config-printer.py crashed with SIGSEGV in strlen@plt() (affects: 4) (dups: 1) (heat: 11)" [Medium,New]
[23:38] <cwillu_at_work> if I install apport, will I get a decent trace out of it?
[23:38] <pcacjr> cwillu_at_work, will take a look. i dunno..
[23:38] <pcacjr> just testing...
[23:39] <cwillu_at_work> I'm browsing for the printer, and it dies when I click on a hostname
[23:39] <cwillu_at_work> the hostnames themselves show up in the workgroup tree though
[23:39]  * pcacjr nods
[23:40] <pcacjr> i'm looking into it right now
[23:49] <cwillu_at_work> pcacjr, booting up a fresh card right now in case the card in question was the problem
[23:51] <cwillu_at_work> okay, it's not the card
[23:52] <cwillu_at_work> might be privilege related
[23:52] <cwillu_at_work> I need to test again, but the first attempt under root worked fine
[23:52] <cwillu_at_work> (I'm generally working as an unprivileged user in lp and lpadmin groups)
[23:52] <cwillu_at_work> I can provide you with ssh access to the box in question if you want
[23:53] <cwillu_at_work> nope, spoke too soon, died on the next machine I clicked on
[23:53] <cwillu_at_work> but that implies that it's not completely deterministic
[23:53] <cwillu_at_work> pcacjr, ^