Le vendredi 04/01/05 Julien BLACHE <[EMAIL PROTECTED]> a �crit :
> > If it could be useful, I can try to recompiled sane with debug
> > information and send a gdb backtrace.
>
> That'd be good, because it doesn't segfault here with my snapscan
> scanner.
Here is the backtrace :
(gdb) exec-file scanimage -L
(gdb) run
Starting program: /usr/bin/scanimage
Using host libthread_db library "/lib/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x300928c4 in mallopt () from /lib/libc.so.6
(gdb) bt
#0 0x300928c4 in mallopt () from /lib/libc.so.6
#1 0x30092768 in mallopt () from /lib/libc.so.6
#2 0x30092768 in mallopt () from /lib/libc.so.6
#3 0x30092768 in mallopt () from /lib/libc.so.6
#4 0x30092768 in mallopt () from /lib/libc.so.6
#5 0x30092768 in mallopt () from /lib/libc.so.6
#6 0x30092768 in mallopt () from /lib/libc.so.6
#7 0x30092768 in mallopt () from /lib/libc.so.6
#8 0x30092768 in mallopt () from /lib/libc.so.6
#9 0x30092768 in mallopt () from /lib/libc.so.6
#10 0x30092768 in mallopt () from /lib/libc.so.6
#11 0x30092768 in mallopt () from /lib/libc.so.6
Previous frame inner to this frame (corrupt stack?)
(gdb)
As you can see there isn't so much information available, does this
mean the problem is in libc?
Or perhaps I made a mistake when recompiling sane-utils?
I have only change the debian/rules file like this :
--- sane-backends-1.0.15/debian/rules 2005-04-01 21:45:35.000000000 +0200
+++ src/sane-backends-1.0.15/debian/rules 2005-04-01 20:55:03.000000000
+0200
@@ -14,12 +14,12 @@
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
DEB_HOST_GNU_SYSTEM ?= $(shell dpkg-architecture -qDEB_HOST_GNU_SYSTEM)
-ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
+#ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
CFLAGS += -g
-endif
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
+#endif
+#ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL_PROGRAM += -s
-endif
+#endif
autotools: autotools-stamp
autotools-stamp:
@@ -168,7 +168,7 @@
# dh_undocumented
dh_installchangelogs ChangeLog
dh_link
- dh_strip
+# dh_strip
dh_compress
dh_fixperms
dh_makeshlibs
and then done a fakeroot debian/rule binary
What can I do now?
Regards.
--
Djoum� SALVETTI
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
