You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Colin Putney <cp...@whistler.net> on 2002/01/08 18:59:47 UTC
Bus Error on Mac OS X (was r727 doesn't build w/ --disable-shared)
On Tuesday, January 8, 2002, at 05:09 AM, Garrett Rooney wrote:
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> 0x00000000 in ?? ()
>> (gdb) bt
>> #0 0x00000000 in ?? ()
>> Cannot access memory at address 0x0
>> #1 0x00065b3c in apr_vformatter (flush_func=0, vbuff=0xbfffec68,
>> fmt=0xc054a " gmt_off %06d)", ap=0xbfffed18 "?\200") at
>
> the problem is that according to what i can read of the source,
> flush_func can't ever be 0... compiler bug or corrupted memory? or
> i'm just reading the source wrong.
That's how I read it too. I even checked the output of cpp to make sure
I wasn't getting tricked by preprocessor sleight-of-hand. I suspect it
could be an issue with linking. Mach-O is a bit quirky relative to ELF...
My next task is to see if the crash is on the first call to
apr_vformatter, or if it only happens sometimes.
-cwp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: Bus Error on Mac OS X (was r727 doesn't build w/ --disable-shared)
Posted by Sander Striker <st...@apache.org>.
> From: Colin Putney [mailto:cputney@whistler.net]
> Sent: 08 January 2002 20:00
> To: svn
> Subject: Bus Error on Mac OS X (was r727 doesn't build w/
> --disable-shared)
>
>
>
> On Tuesday, January 8, 2002, at 05:09 AM, Garrett Rooney wrote:
>
> >> Program received signal EXC_BAD_ACCESS, Could not access memory.
> >> 0x00000000 in ?? ()
> >> (gdb) bt
> >> #0 0x00000000 in ?? ()
> >> Cannot access memory at address 0x0
> >> #1 0x00065b3c in apr_vformatter (flush_func=0, vbuff=0xbfffec68,
> >> fmt=0xc054a " gmt_off %06d)", ap=0xbfffed18 "?\200") at
> >
> > the problem is that according to what i can read of the source,
> > flush_func can't ever be 0... compiler bug or corrupted memory? or
> > i'm just reading the source wrong.
>
> That's how I read it too. I even checked the output of cpp to make sure
> I wasn't getting tricked by preprocessor sleight-of-hand. I suspect it
> could be an issue with linking. Mach-O is a bit quirky relative to ELF...
flush_func should never be NULL AFAIK.
> My next task is to see if the crash is on the first call to
> apr_vformatter, or if it only happens sometimes.
That would be weirdness. Can you post the rest of that bt?
> -cwp
Sander 'tired, so may be spewing nonsense'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org