Dear People,
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252517
I'd like to ask for help in debugging this. Firstly, can anyone
reproduce this on sarge?
When I run inside gdb I don't get any information about the segfault,
presumably because I don't have python2.3 compiled with debugging support
I tried to compile python2.3 with debugging support. I made what I
thought were appropriate changes in rules (see patch below).
However, when I try to do *anything* with the resulting executable, I
get errors, eg. something about cannot import site (whatever that
means), and I cannot load the numarray shared libraries.
Should I be doing things differently? Should I be compiling numarray
with debugging support? Any other suggestions?
Faheem.
--- rules 2004-06-07 14:44:28.000000000 -0400
+++ rules.new 2004-06-07 14:46:32.000000000 -0400
@@ -89,16 +89,16 @@
stamp-build-static: stamp-configure-static
dh_testdir
- $(MAKE) -C $(buildd_static)
+ $(MAKE) OPT=-g -C $(buildd_static)
touch stamp-build-static
stamp-build-shared: stamp-configure-shared
dh_testdir
: # build the shared library
- $(MAKE) -C $(buildd_shared) \
+ $(MAKE) OPT=-g -C $(buildd_shared) \
libpython$(VER).so
: # build a static library with PIC objects
- $(MAKE) -C $(buildd_shared) \
+ $(MAKE) OPT=-g -C $(buildd_shared) \
LIBRARY=libpython$(VER)-pic.a libpython$(VER)-pic.a
touch stamp-build-shared
@@ -107,7 +107,8 @@
--with-fpectl \
--enable-ipv6 \
--enable-unicode=ucs4 \
- --without-cxx
+ --without-cxx \
+ --with-pydebug
stamp-configure-shared: patch-stamp
mkdir -p $(buildd_shared)
@@ -136,7 +137,7 @@
stamp-check:
@echo "BEGIN test"
- -$(MAKE) -C $(buildd_static) test TESTOPTS="-l -unetwork,bsddb" 2>&1 \
+ -$(MAKE) OPT=-g -C $(buildd_static) test TESTOPTS="-l -unetwork,bsddb"
2>&1 \
| tee debian/test_results
@echo "END test"
touch stamp-check
