Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-05-22 Thread Riku Voipio
block 469863 by 469517 thanks pidgin uses -fstack-protector, which is broken on arm and armel :( If you don't want to add a special case for DEB_HOST_ARCH_CPU=arm in debian/rules, you can look at hardening-wrapper for alternative of setting hardened paramaters. -- "rm -rf" only sounds scary if y

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-25 Thread Alan Krempler
Ari Pollak <[EMAIL PROTECTED]> wrote: > tags 469863 +unreproducible > > Some help in tracking this bug down would be appreciated, since I have > no real way to test or debug pidgin on armel. I have an armel system, but I don't have the knowledge nor the time for real debugging. However, I'll be

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-24 Thread Ari Pollak
tags 469863 +unreproducible Some help in tracking this bug down would be appreciated, since I have no real way to test or debug pidgin on armel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-10 Thread Alan Krempler
this is the backtrace of finch segfaulting: Starting program: /usr/bin/finch [Thread debugging using libthread_db enabled] [New Thread 0x400228f0 (LWP 14686)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x400228f0 (LWP 14686)] 0x401cb400 in purple_core_migrate () at

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-10 Thread Alan Krempler
On Sun, 09 Mar 2008 15:29:04 -0400 Ari Pollak <[EMAIL PROTECTED]> wrote: > This doesn't make much sense since it seems to be in the ~/.gaim > migration code, and that hasn't changed in a while. Could you run pidgin > with MALLOC_CHECK_=3 set and see if you get a better backtrace? > Still the sam

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-09 Thread Ari Pollak
This doesn't make much sense since it seems to be in the ~/.gaim migration code, and that hasn't changed in a while. Could you run pidgin with MALLOC_CHECK_=3 set and see if you get a better backtrace? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Conta

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-09 Thread Alan Krempler
Starting program: /usr/bin/pidgin [Thread debugging using libthread_db enabled] [New Thread 0x410b3580 (LWP 8314)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x410b3580 (LWP 8314)] 0x406f6400 in purple_core_migrate () at ../../libpurple/core.c:412 412 ../../li

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-07 Thread Ari Pollak
Could you install libgtk2.0--0-dbg and pidgin-dbg and get a backtrace? Instructions are here, but you can skip the rebuilding section: http://wiki.debian.org/HowToGetABacktrace -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#469863: pidgin and finch segfault on startup (armel arch)

2008-03-07 Thread Alan Krempler
Package: pidgin Version: 2.4.0-1 Severity: important Both pidgin and finch segfault immediately on startup, without any other output on the console before the segfault message. Deleting ~/.purple/prefs.xml did not help. Note: architecture is armel. Version 2.3.1 works ok. -- System Information: