On Sun, Nov 13, 2011 at 05:15:59PM -0500, Richard Hipp wrote: > 2011/11/13 Lluís Batlle i Rossell <[email protected]> > > > It should be quite tricky C code for a > > C compiler to generate bad-aligned accesses for a given platform. I'd like > > to > > know where is that bad access; I've not checked, but I'd imagine fossil > > has no > > tricky C code. > > > > Fossil doesn't have any tricky C code (or at least it shouldn't - if you > find some we'll call it a bug.) But SQLite does definitely have tricky C > code. We've had SIGBUS problems running SQLite on sparc before, but I > thought we had fixed all those. On the other hand, I don't have sparc on > which to test SQLite so I'm not really sure.
There are some candidates I can think of. The easiest is definitely to just run gdb on a debug build and report the back trace of the crash. > I know we don't have alignment problems on PPC, but I don't know if PPC is > as fussy about alignment as Sparc is.... It isn't. (Older) ARM and SPARC are the most interesting platforms when it comes to strict alignment. PPC is normally configured to not trap, just like x86. Joerg _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
