On Sun, Nov 13, 2011 at 10:10 PM, Julian Fagir <[email protected]>wrote:

> Having to register to send mails to the list (and especially getting no
> reports) is somewhat... unintuitive.
>

i can't even guess as to why the mailing list hasn't been working for you.


> > Updating sqlite3? Are you linking it with a custom version instead of the
> > one which is part of the fossil distro?
> I'm sorry I don't remember that anymore. It didn't work, then I updated
> sqlite3, then recompiled it, then it worked.
>

When you say "updated sqlite3", what exactly do you mean? Fossil has its
own embedded copy. Did you replace that one (under src/sqlite3.*) with one
you got from somewhere else?

There are three files attached:
>  * configure log of 1.20
>  * ktruss of 1.20 coredumping
>

This part:

11868      1 fossil   write(0x5, 0x40b16808, 0x200) = 512, 1085368328

 
"\0\0\0\0\0\0\0\0\0\0\0\0\M-/\M^H\M-66\0\0\0\0\0\0\^B\0\0\0\^D\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
 11868      1 fossil   SIGBUS SIG_DFL

As best as i can tell that's your OS segfaulting, not fossil. It returns
from a write() and then immediately throws a sigbus? sigbus is something
i've only seen on sparc, and i've personally only seen it when linking to
invalid system libs (e.g. those compiled for other platforms). A bit of
googling shows sigbus to sometimes be alignment-related. The address being
passed to write() is 0x40b16808 (dec=1085368328), which "should" be
properly aligned for 32/64-bit.

Can you run it through gdb (or the platform's equivalent) and give us a
backtrace after the crash?

Other googling suggests that a cast in one part of the code can cause
corruption which first shows up as a sigbus further downstream. Could you
run it through valgrind? That would help us rule out memory corruption.

 * ktruss of 1.18 complaining about manifest file
>

1.18 is "ancient" and won't tell us much - a lot has happened since then.

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to