On Sat, Jul 28, 2007, Paul Colomiets wrote:
>
> [...]
Because I can't resist: shouldn't that be a "truck error" if you're using
transformer.py?
For those who don't get it:
http://en.wikipedia.org/wiki/Transformers_%28fiction%29
--
Aahz ([EMAIL PROTECTED]) <*> http://www.pytho
> Thanks a lot. I think I'll set up it in sitecustomize.py.
> I don't know but maybe you should consider change platform defaults.
Such a patch should be contributed by a FreeBSD expert. Different
versions of FreeBSD behave differently, with too many conditions to
consider. It's a mess. The simple
Martin v. Löwis wrote:
> You should run it under gdb, or attach to the interpreter
> from gdb.
>
I've run it with gdb before (when posted a bug),
and sometimes I got a huge traceback with
1+ lines and sometimes less than 100
full of question marks so I've decided it's not of
a great interes
> Any hints how to debug it further?
You should run it under gdb, or attach to the interpreter
from gdb.
Could it be that you get a stack overflow? To my knowledge,
stack space is very scarce on FreeBSD if you use threads.
Regards,
Martin
___
Python-D
Paul> And I feel that It's bug in python, or python port, because I'm
Paul> getting Bus error on some stage when I'm tracing execution and
Paul> trying to backtrace.
Have you run it under control of a C-level debugger (gdb, dbx, etc) to see
where the bus error occurs?
Skip
_
Hi!
I'm still working on bug:
http://python.org/sf/1720241
First thing I've found is that `compile` works OK, but `compiler.parse` not.
And I feel that It's bug in python, or python port, because I'm getting
Bus error
on some stage when I'm tracing execution and trying to backtrace. Also
`pars
