I had a similar issue with Bus error: 10 Turned out to be an infinite depth recursion loop like James says. My recommendation for anyone who encounters this it to create a unit test for the specific situation that causes it or play around with it using "./manage.py shell". You may be able to find a proper exception message.
On Monday, April 23, 2012 12:36:19 PM UTC-6, James wrote: > > I found the problem. I had overridden __getattr__ and returned > self.value which did not yet exist on the object. This caused a > maximum recursion depth RuntimeError. I'm still not sure why this > became "Bus error: 10", however. > > James Leard > > On Apr 23, 1:31 pm, Nikolas Stevenson-Molnar <nik.mol...@consbio.org> > wrote: > > I would try reinstalling Python and Django. This seemed to resolve the > > issue of the original poster. > > > > _Nik > > > > On 4/21/2012 3:18 PM, James wrote: > > > > > > > > > > > > > > > > > I just started receiving the same error "Bus error: 10". I made a > > > small code change and > > > it suddenly appeared. I've reverted but that doesn't seem to matter. > > > Very odd behavior. > > > I'll continue debugging. My settings: > > > > > Python 2.7.1 > > > OS:X Lion 10.7.3 > > > Django 1.4.0 > > > > > James Leard > > > > > On Apr 20, 7:58 am, Tom Evans <tevans...@googlemail.com> wrote: > > >> On Thu, Apr 19, 2012 at 5:11 PM, Harald Sigh Andertun > > > > >> <harald.ander...@gmail.com> wrote: > > >>> I'm sorry. Actually that was not the solution. It works sometimes > now, which > > >>> it didn't before. I'll attach a screenshot. > > >>> I'm on mac (OS X Lion). > > >> A bus error occurs due to unaligned memory access, or access to a non > > >> existent memory address. In the absence of an actual bug (which > others > > >> would see), this clearly indicates that one or another of the C > > >> libraries used by python conflicts with it. > > > > >> This could happen if you compiled a C library to use with python, > like > > >> one of the many python packages that consist of a small C library > > >> (mysql and postgresql DB adaptors, PIL, many others), and use it with > > >> a different python than it was compiled against. > > > > >> It probably has very little to do with django - django is pure python > > >> - but with one of the libraries that is used by django or your code. > > >> The solution is simple; remove everything, start from scratch and > > >> recompile/reinstall everything relevant. > > > > >> It is probably trickier as OS X does interesting things with python, > > >> and most users end up with a system python and a user python. Making > > >> sure your installed extensions are compiled and used with the right > > >> python is then what is important. > > > > >> Cheers > > > > >> Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
