Processing commands for [EMAIL PROTECTED]:
tags 427256 patch
Bug#427256: reproducible crash when searching (x86_64 only)
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On Fri, 8 Jun 2007, Robert Millan wrote:
On Fri, Jun 08, 2007 at 08:35:10PM +0200, Reuben Thomas wrote:
If you single-step in gdb from the call to search_forward you should be
able to see where bogosity sets in. (But don't worry about that too much; a
correct backtrace is the main thing, I
On Tue, 5 Jun 2007, Robert Millan wrote:
On Mon, Jun 04, 2007 at 10:54:52AM +0200, Reuben Thomas wrote:
Could I have a gdb backtrace (and a valgrind trace if that works on
x86_64)?
gdb backtrace:
#0 0x00411aa2 in search_forward (startp=0x55e9a0, starto=0,
s=0x55d7e1 a, regexp=0)
On Fri, Jun 08, 2007 at 08:35:10PM +0200, Reuben Thomas wrote:
If you single-step in gdb from the call to search_forward you should be
able to see where bogosity sets in. (But don't worry about that too much; a
correct backtrace is the main thing, I think.)
With CVS from just a few minutes
On Sat, 2 Jun 2007, Robert Millan wrote:
Package: zile
Version: 2.2.31-1
Severity: grave
If you edit the attached ca.po (obtained from totem svn) on an x86_64 system,
and try to search something (in my test, ), zile will crash.
Could I have a gdb backtrace (and a valgrind trace if that
On Mon, Jun 04, 2007 at 10:54:52AM +0200, Reuben Thomas wrote:
On Sat, 2 Jun 2007, Robert Millan wrote:
Package: zile
Version: 2.2.31-1
Severity: grave
If you edit the attached ca.po (obtained from totem svn) on an x86_64
system,
and try to search something (in my test, ), zile
6 matches
Mail list logo
