Re: Balsa crashes on startup

["tom" <tom osageinc com>]

Subject: Re: Balsa crashes on startup
Date: Thu, 30 Oct 2003 19:59:30 -0000
From: "Tom Lamm" <tlamm@osageinc.com>
To: Pawel Salek <pawsa@theochem.kth.se>, tom <tom@osageinc.com>


The stack trace follows. I installed from the .deb files at the debian ftp site, so no debugging information is turned on.

It crashes on startup, so there are no user actions required to cause the problem. Again, it works if I am root. I figured somebody would take that clue to remind me of a really stoopid permissions type of problem.

Tom Lamm


GNU gdb 6.0-debian
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
(gdb) run --disable-crash-dialg
Starting program: /usr/bin/balsa --disable-crash-dialg
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found).(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)..(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)..(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 6681)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found).(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 6681)]
0x411443a3 in strrchr () from /lib/libc.so.6
(gdb) bt
#0  0x411443a3 in strrchr () from /lib/libc.so.6
#1  0x080e2fab in libbalsa_server_load_config ()
#2  0x0000003a in ?? ()
(gdb) list
------------------------------------------------------
There is no symbol table, so the list, up, local, etc.. have no information

Tom



---------- Original Message -------------
Subject: Re: Balsa crashes on startup
Date: Thu, 30 Oct 2003 19:17:35 +0100
From: Pawel Salek <pawsa@theochem.kth.se>
To: tom <tom@osageinc.com>



On 10/30/2003 06:19:51 AM, tom wrote:
> [snip]
> When I load Balsa from a terminal, as a user, it displays the
> 
> *** Message: init gpgme version 0.3.15
> 
> message and then crashes with a seg-fault.

Do you think you could provide a stack trace? You can find instructions  
at http://balsa.gnome.org/bugs.html

Pawel
_______________________________________________
balsa-list mailing list
balsa-list@gnome.org
http://mail.gnome.org/mailman/listinfo/balsa-list