On Tue, 29 Apr 2008 09:20:04 +0100, Chris Lale wrote:
Jeff Kowalczyk wrote:
On Mon, 28 Apr 2008 21:01:08 -0400, m. allan noah wrote:
well, i've just committed a patch to fix this, but please test, as i
never saw the error message in the first place...
Does anyone have a good procedure for
Hi,
Julien BLACHE wrote:
Gah, that damn crash reporter is getting in the way. Can you try to
get rid of it?
You have to set the env variable MALLOC_CHECK_ to 0, i.e., in bash
export MALLOC_CHECK_=0
or in tcsh
setenv MALLOC_CHECK_ 0
then you will get a proper backtrace with gdb..
Hi,
I guess the bug is that in sane_close the scanner_devList entry
corresponding to the open handle is destroyed, and later in sane_exit
all scanner_devList entries are destroyed again.
I guess in sane_close, the entry should be be destroyed, but only marked
as free or so.
regards
-- jochen
Jeff Kowalczyk wrote:
On Mon, 28 Apr 2008 21:01:08 -0400, m. allan noah wrote:
well, i've just committed a patch to fix this, but please test, as i
never saw the error message in the first place...
Does anyone have a good procedure for patching and rebuilding
released ubuntu .debs to test
Jeff Kowalczyk jtk at yahoo.com wrote:
Hi,
$ scanimage -d epjitsu
(massive ansi terminal spew)
*** glibc detected *** scanimage: double free or corruption (!prev):
0x08053ca0 ***
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6[0xb7e7fa85]
On Mon, 28 Apr 2008 21:51:50 +0200, Julien BLACHE wrote:
Jeff Kowalczyk jtk at yahoo.com wrote:
Hi,
$ scanimage -d epjitsu
(massive ansi terminal spew)
*** glibc detected *** scanimage: double free or corruption (!prev):
0x08053ca0 ***
=== Backtrace: =
Jeff Kowalczyk jtk at yahoo.com wrote:
Hi,
$ gdb scanimage
run -d epjitsu
(some messages, then terminal data spew)
*** glibc detected *** /usr/bin/scanimage: corrupted double-linked list:
0x08054120 ***
(no debugging symbols found)
=== Backtrace: =
On Mon, 28 Apr 2008 23:10:51 +0200, Jochen Eisinger wrote:
export MALLOC_CHECK_=0
If possible, use valgrind -v scanimage -d epjitsu to generate the
backtrace, it will be more informative.
gdb terminal spew hit a magic ansi sequence that made the text unreadable.
If you can suggest a command
well, i've just committed a patch to fix this, but please test, as i
never saw the error message in the first place...
allan
On 4/28/08, m. allan noah kitno455 at gmail.com wrote:
ouch- i go away for a few hours, and my code grows bugs, and gets valgound :)
i think Jochen hit the nail on the
On Mon, 28 Apr 2008 21:01:08 -0400, m. allan noah wrote:
well, i've just committed a patch to fix this, but please test, as i
never saw the error message in the first place...
Does anyone have a good procedure for patching and rebuilding
released ubuntu .debs to test upstream changes? Or a way
10 matches
Mail list logo
