[Bioc-devel] affxparser: Core dump with R 2.14.x on OSX [take #2]
hb at biostat.ucsf.edu
Sat Jan 21 00:20:29 CET 2012
[bringing back to the list, because we could need some help from other
developers with access to various OSX versions]
thanks for looking into this.
On Fri, Jan 20, 2012 at 2:17 PM, Dan Tenenbaum <dtenenba at fhcrc.org> wrote:
> On Fri, Jan 20, 2012 at 1:57 PM, Dan Tenenbaum <dtenenba at fhcrc.org> wrote:
>> On Fri, Jan 20, 2012 at 1:44 PM, Dan Tenenbaum <dtenenba at fhcrc.org> wrote:
>>> Hi Henrik,
>>> On Fri, Jan 20, 2012 at 10:33 AM, Henrik Bengtsson <hb at biostat.ucsf.edu> wrote:
>>>> this is a kind request for the BioC team to have another look at
>>>> fixing the binary affxparser builds. Quite a few OSX users on R
>>>> v2.14.0 have R crashing because of this problem.
>>> Thanks for the prompt and the detailed problem report.
>>>> Since thread 'Re: [Bioc-devel] affxparser: Core dump with R 2.14.0 on
>>>> OSX' on Nov 7, 2011
>>>> became cluttered with mistakes, I'm starting a new thread on the same
>>>> The binary build of affxparser v1.26.2 for OSX provided by
>>>> Bioconductor is broken and causes R v2.14.0 to crash ("core dump",
>>>> "abort trap", ...) on OSX 10.6 ("Snow Leopard") and (I assume; someone
>>>> please confirm) OSX 10.7 ("Lion"),
>>> I can confirm that it happens on Lion too.
>>>> but not OSX 10.5 ("Leopard"). A
>>>> reproducible example is:
>>>> which should return a named header. (Download CDF file:
>>>> ; 2.2Mb). Another example is
>>>> CURRENT WORKAROUNDS:
>>>> - Install affxparser from source
>>>> - Install Kasper Hansen's binary build (not universal?)
>>>> [http://www.braju.com/R/repos/osx_10.6/affxparser_1.26.2.tgz] that
>>>> works on (at least) OSX 10.6.8.
>>>> See also aroma.affymetrix thread 'OSX 10.6 & 10.7 users: Workaround
>>>> for faulty BioC build of affxparser v1.26.2' on Jan 14, 2012
>>>> I can confirm that installing from source, works on an OSX 10.6.8
>>>> machine with R v2.14.1
>>>> (http://cran.r-project.org/bin/macosx/R-2.14.1.pkg). Installing
>>>> Kasper's binary build also works. I've a limited understanding on the
>>>> different types of OSX package binaries, only access to OSX 10.6.8,
>>>> making it hard for me to do any more troubleshooting, but as far as I
>>>> understand there is something wrong with the way affxparser is build
>>>> on the Bioconductor servers.
>>> An important fact to bear in mind is that the BioC Mac build servers
>>> are running Leopard (OS X 10.5.8).
>>> It's a bit tricky to debug since it works fine on the platform it's
>>> built on...but using primitive means (Rprintf() statements), I was
>>> able to narrow down the problem to the
>>> function in
>>> In that function, the expression
>>> if (fileMagicNumber != DATA_FILE_MAGIC_NUMBER)
>>> evaluates to true, and therefore an
>>> affymetrix_calvin_exceptions::InvalidFileTypeException is thrown.
>>> I don't really know why the magic number is wrong, or would vary
>>> between operating systems, but perhaps this gives you something to go
>>> BTW, the trace is:
>>> R: readCdfHeader()
>>> Hope this helps. If I can be of assistance in further debugging this,
>>> please let me know.
>> I should also have mentioned that in the ReadMagicNumber() function,
>> fileMagicNumber == 67
>> with the file Mapping10K_Xba142.cdf, and the expected magic number is 59.
> Sorry for all the emails, but here's one more piece of info:
> If I run the package with the debug statements on pitt, our Leopard
> build machine, it works fine, as expected, but it also reports that
> fileMagicNumber is 67. So the exception is still thrown, but execution
So when "execution continues" despite the incorrect magic number, do
still get a valid CDF header readout at the R prompt?
> Whereas on my Lion machine, execution ends (after a pause) with "Abort trap: 6".
> So I am not sure whether this exception is really part of the problem,
> or just a red herring.
It could be a red herring; the incorrectly read magic header (first
byte in the file) is just a side effect of something more complicated,
but it is definitely a start. It is also a hint that we could/should
update affxparser to at least catch this and give an error instead of
crashing (but I'm sure if we should play with such updates, while
troubleshooting the real cause).
There is one more important clue available. This problem started to
occur with BioC 2.9 and R v2.14.x. Previous BioC builds of affxparser
did not cause this, and by even forcing an installation of the old
affxparser v1.24.0 binaries on R v2.14.1 on OSX 10.6.8:
it works. So, something "happened" between:
Packaged: 2011-04-15 09:35:06 UTC; biocbuild
Built: R 2.13.0; universal-apple-darwin9.8.0; 2011-04-15 16:46:28 UTC; unix
Archs: i386, ppc, x86_64
Packaged: 2011-11-17 06:38:13 UTC; biocbuild
Built: R 2.14.0; universal-apple-darwin9.8.0; 2011-11-17 15:39:53 UTC; unix
Archs: i386, ppc, x86_64
(the first known report on this problem is from Nov 7, 2011
[http://goo.gl/ZqBsW], which is before the date of the latter). There
is only one real update in affxparser v1.26.1, but that is in pure R
code and more importantly not in code used in this bug report. So,
rebuilding affxparser v1.24.0 on the BioC server will most likely
cause the same crash as affxparser v1.26.2 does.
BTW, are you planning to update to R v2.14.1 on the BioC OSX servers?
With some luck, maybe that will fix it.
It would be great if someone else with OSX 10.5.8 ("Leopard") could
build/install affxparser v1.26.2 from source are share it with us for
testing on OSX 10.6 & 10.7; that would help narrow down the source of
the problem. If such a build works, then it is much more likely that
there is something with the BioC OSX 10.5.8 server setup, whereas if
it also crashes, then we might have to search for the problem
> Hope this is helpful....
>>>> Bioc-devel at r-project.org mailing list
More information about the Bioc-devel