Alex Roitman wrote:
On Wed, 2005-10-26 at 21:33 -0500, Jeffrey Hundstad wrote:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210210624 (LWP 10033)]
0xb7e49b2b in strlen () from /lib/tls/i686/cmov/libc.so.6
[snip]
Since it segfaulted in the i686 libraries I'll include this one too:
ii libc6-i686 2.3.5-7 GNU C Library: Shared libraries [i686
optimized]
This does not seem to be GRAMPS bug. Nothing we do from
within python should be able to cause segfault. Such
things are between Python and the C libs.
Have you built your own python?
No, this is the Debian Python:
ii python 2.3.5-3 An interactive high-level object-oriented language
(default version)
Does the issue go away if you remove libc6-i686 package?
Nope, I still get:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209989440 (LWP 3215)]
0xb7e800cb in strlen () from /lib/tls/libc.so.6
I did SUCCESSFULLY install and run gramps on my i686 laptop. Sigh... I
must be something specific with my desktop machine. Here's the cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 4
model name : AMD Athlon(tm) 64 Processor 2800+
stepping : 10
cpu MHz : 1871.978
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm
3dnowext 3dnow
bogomips : 3746.86
The cpu is running in 32 bit mode without the 64 bit libraries installed
(but the 64 bit libraries installed doesn't change things.)
Any clue where to look?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
