Hi,

On Mon, Aug 31, 2009 at 03:42:39AM +0200, Per Hansen wrote:
> Ryan Niebur schrieb:
> > Per, do you still get this problem?
> 
> Uhh this is a old one!
> I tried to replicate the problem via ssh on a lenny server.
> Installed gq_1.0.0-3+b1_amd64.deb and was able to reproduce the crash!
> 
> Later I tried to create a backtrace with "LANG=C gdb gq", but was unable
> to crash the client!
> 
> It seems to be a problem with the system-encoding / UTF...
> 

ah. that explains why only some people can reproduce it.

> 
> > if so, can you please provide a
> > gdb backtrace?
> 
> Yes, if you can live with the missing debugging symbols...
> 

okay, that's not very useful.
would you mind locally rebuild gq with debug symbols and getting the trace 
again?

running these commands should rebuild and install it with debugging symbols:
sudo apt-get install --no-install-recommends build-essential dpatch 
libgtk2.0-dev libldap2-dev libkrb5-dev libxml2-dev libsasl2-dev libssl-dev 
devscripts wget gnupg debian-keyring libdigest-md5-perl
dget ftp://ftp.debian.org/debian/pool/main/g/gq/gq_1.0.0-3.dsc
cd gq-1.0.0
DEB_BUILD_OPTIONS=nostrip dpkg-buildpackage -us -uc
sudo dpkg -i ../gq_1.0.0-3_amd64.deb

> 
> BTW.
> With the experimental gq_1.2.2-2_amd64.deb I am unable to connect to any
> of the ldap server I know...
> 

ya, the version in experimental and the latest upstream don't work for
me either.

Thanks,
Ryan

-- 
_________________________
Ryan Niebur
ryanrya...@gmail.com

Attachment: signature.asc
Description: Digital signature

Reply via email to