On Thu, 2011-05-05 at 20:44 +0200, Matthias Apitz wrote:
> Should I wait for some kind of fix for 2.32.x?
Try this:
diff --git a/libebackend/e-data-server-module.c
b/libebackend/e-data-server-module.c
index 52fb35b..d5c27e7 100644
--- a/libebackend/e-data-server-module.c
+++ b/libebackend/e-dat
El día Thursday, May 05, 2011 a las 05:16:11PM +0100, David Woodhouse escribió:
> On Thu, 2011-05-05 at 13:30 +0200, Matthias Apitz wrote:
> > as you can see e2k_ascii_strcase_hash() is in two shared libs and with
> > the same last bits of the correct addr and the broken addr; as I wild
> > guess
On Thu, 2011-05-05 at 13:30 +0200, Matthias Apitz wrote:
> as you can see e2k_ascii_strcase_hash() is in two shared libs and with
> the same last bits of the correct addr and the broken addr; as I wild
> guess I simply renamed 'libecalbackendexchange.so' to get it out of the
> way; the e-calendar-f
>
> I think we're getting somewhere :-)
I think I catched the beast:
I checked in /proc/PID/map where the two addr are:
(gdb) p *hash_table
$2 = {size = 8, mod = 7, mask = 7, nnodes = 0, noccupied = 0,
nodes = 0x29972d60, hash_func = 0x29ed1f6b, key_equal_func = 0x29ed1f39,
ref_count = 1, v
El día Wednesday, May 04, 2011 a las 11:48:05AM +0100, David Woodhouse escribió:
> On Wed, 2011-05-04 at 12:45 +0200, Matthias Apitz wrote:
> > > That would seem to imply that your hash table was buggered from the very
> > > beginning. If you really can't get gdb to work properly and use a
> > > h
El día Wednesday, May 04, 2011 a las 11:48:05AM +0100, David Woodhouse escribió:
> On Wed, 2011-05-04 at 12:45 +0200, Matthias Apitz wrote:
> > > That would seem to imply that your hash table was buggered from the very
> > > beginning. If you really can't get gdb to work properly and use a
> > > h
On Wed, 2011-05-04 at 12:45 +0200, Matthias Apitz wrote:
> > That would seem to imply that your hash table was buggered from the very
> > beginning. If you really can't get gdb to work properly and use a
> > hardware watchpoint, try littering similar printfs all the way through
> > g_hash_table_new
El día Wednesday, May 04, 2011 a las 10:52:03AM +0100, David Woodhouse escribió:
> On Wed, 2011-05-04 at 11:44 +0200, Matthias Apitz wrote:
> > I have inserted some fprintf's in read_conf() to print in hex the memory
> > of the hash_table (see below); it matches what gdb reads about the
> > hash_t
On Wed, 2011-05-04 at 11:44 +0200, Matthias Apitz wrote:
> I have inserted some fprintf's in read_conf() to print in hex the memory
> of the hash_table (see below); it matches what gdb reads about the
> hash_table (values marked with ^^^);
Was that *right* after the g_hash_table_new() call?
Tha
El día Friday, April 29, 2011 a las 10:48:46AM +0200, Matthias Apitz escribió:
> El día Thursday, April 28, 2011 a las 04:13:40PM +0100, David Woodhouse
> escribió:
>
> > On Thu, 2011-04-28 at 16:54 +0200, Matthias Apitz wrote:
> > >
> > > I've rebuild glib-2.26.1 and evo-exchange 2.32.3 (remov
El día Tuesday, May 03, 2011 a las 01:52:07PM +0200, Matthias Apitz escribió:
> El día Monday, May 02, 2011 a las 04:03:13PM +0200, Milan Crha escribió:
>
> > On Wed, 2011-04-27 at 08:22 +0200, Matthias Apitz wrote:
> > > (gdb) bt
> > > #0 0x29ddaa30 in ?? ()
> > > #1 0x290b754b in g_hash_table
El día Monday, May 02, 2011 a las 04:03:13PM +0200, Milan Crha escribió:
> On Wed, 2011-04-27 at 08:22 +0200, Matthias Apitz wrote:
> > (gdb) bt
> > #0 0x29ddaa30 in ?? ()
> > #1 0x290b754b in g_hash_table_lookup ()
> > from /usr/local/lib/libglib-2.0.so.0
> > #2 0x29f46c26 in e2k_autoconfig_lo
On Wed, 2011-04-27 at 08:22 +0200, Matthias Apitz wrote:
> (gdb) bt
> #0 0x29ddaa30 in ?? ()
> #1 0x290b754b in g_hash_table_lookup ()
> from /usr/local/lib/libglib-2.0.so.0
> #2 0x29f46c26 in e2k_autoconfig_lookup_option (
> option=0x29f79ea0 "Disable-Plaintext") at e2k-autoconfig.c:1472
Do you guys know how to use irc?
--
Gary Dunn, Honolulu
Open Slate Project
http://openslate.org
http://www.facebook.com/garydunn808
http://e9erust.blogspot.com
Twitter @garydunn808
Sent from my Android phone with K-9 Mail.
Matthias Apitz wrote:
El día Thursday, April 28, 2011 a las 03:03:29PM
On Fri, 2011-04-29 at 10:48 +0200, Matthias Apitz wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 29804300 (LWP 101032/initial thread)]
> 0x29e55d87 in ?? ()
> (gdb) bt
> #0 0x29e55d87 in ?? ()
> #1 0x2910fb4d in g_hash_table_lookup_node (hash_table=0x29850e90
El día Thursday, April 28, 2011 a las 04:13:40PM +0100, David Woodhouse
escribió:
> On Thu, 2011-04-28 at 16:54 +0200, Matthias Apitz wrote:
> >
> > I've rebuild glib-2.26.1 and evo-exchange 2.32.3 (removing my changes)
> > with gcc46; the problem remains:
> >
> > Server is up and running...
>
On Thu, 2011-04-28 at 06:12 -1000, Open Slate Project wrote:
> Do you guys know how to use irc?
Yes, thank you.
Although I find it to be a very suboptimal medium for receiving gdb
backtraces.
Not anywhere near as suboptimal as the copy of the backtrace that you
for some reason chose to include i
El día Thursday, April 28, 2011 a las 06:12:04AM -1000, Open Slate Project
escribió:
> Do you guys know how to use irc?
> --
>
> Gary Dunn, Honolulu
> Open Slate Project
> http://openslate.org
> http://www.facebook.com/garydunn808
> http://e9erust.blogspot.com
> Twitter @garydunn808
> Sent from
On Thu, 2011-04-28 at 16:54 +0200, Matthias Apitz wrote:
>
> I've rebuild glib-2.26.1 and evo-exchange 2.32.3 (removing my changes)
> with gcc46; the problem remains:
>
> Server is up and running...
> [Thread 2997d200 (LWP 100749/e-calendar-factory) exited]
>
> Program received signal SIGSEGV, S
On Thu, 2011-04-28 at 16:59 +0200, Matthias Apitz wrote:
> Good opinion. Will someone take care about a bug in such an old version
> 2.32.3 which aparently only shows up in FreeBSD HEAD?
>
> I know that the following does not help, but I want to mention that if I
> can't fix this I have to stay wi
El día Thursday, April 28, 2011 a las 04:45:45PM +0200, Milan Crha escribió:
> > yes; I will rebuild it with gcc466... hang on;
>
> Hi,
> even it's an interesting reading, what about filling a bug in Gnome's
> bugzilla and move this bug-hunting there? Just my opinion.
> Bye,
> M
El día Thursday, April 28, 2011 a las 03:03:29PM +0100, David Woodhouse
escribió:
> On Thu, 2011-04-28 at 16:01 +0200, Matthias Apitz wrote:
> >
> > yes; I saw this as well and checked config_options with fprinf's;
> > after
> > the 1st call of read_config() it contains a good point, but even wi
On Thu, 2011-04-28 at 16:11 +0200, Matthias Apitz wrote:
> > > return g_hash_table_lookup (config_options, option);
> > > to
> > > return NULL;
> > >
> > > I don't know why g_hash_table_lookup() crashes;
> >
> > Was your glib built with the old, buggered, compiler?
>
> yes; I will rebu
El día Thursday, April 28, 2011 a las 03:03:29PM +0100, David Woodhouse
escribió:
> On Thu, 2011-04-28 at 16:01 +0200, Matthias Apitz wrote:
> >
> > yes; I saw this as well and checked config_options with fprinf's;
> > after
> > the 1st call of read_config() it contains a good point, but even wi
On Thu, 2011-04-28 at 16:01 +0200, Matthias Apitz wrote:
>
> yes; I saw this as well and checked config_options with fprinf's;
> after
> the 1st call of read_config() it contains a good point, but even with
> this g_hash_table_lookup() crashes; that's why I changed the line
>
> return g_hash
El día Thursday, April 28, 2011 a las 02:42:44PM +0100, David Woodhouse
escribió:
> On Thu, 2011-04-28 at 15:13 +0200, Matthias Apitz wrote:
> >
> >
> > but read_config () can't find the file /usr/local/etc/connector.conf
> > and just returns (line 1412) to e2k_autoconfig_lookup_option() which
On Thu, 2011-04-28 at 15:13 +0200, Matthias Apitz wrote:
>
>
> but read_config () can't find the file /usr/local/etc/connector.conf
> and just returns (line 1412) to e2k_autoconfig_lookup_option() which
> makes the g_hash_table_lookup() crashing later;
I don't understand. The *first* think that
El día Thursday, April 28, 2011 a las 09:38:58AM +0200, Matthias Apitz escribió:
> Compiling evo-exchange 2.32.3 works fine with gcc466:
>
> # make CFLAGS='-g' CC=gcc46 STRIP=' ' install
>
> but crashes with the same backtrace when calendar is picked up in Evo.
I think I have localizated the bu
El día Wednesday, April 27, 2011 a las 08:22:17AM +0200, Matthias Apitz
escribió:
> El día Tuesday, April 26, 2011 a las 11:39:20PM +0200, Matthias Apitz
> escribió:
>
> > I think we have now the two options and I will try them in this order:
> >
> > 1)
> > get evo-exchange 2.32.1 compiled wit
El día Tuesday, April 26, 2011 a las 11:39:20PM +0200, Matthias Apitz escribió:
> I think we have now the two options and I will try them in this order:
>
> 1)
> get evo-exchange 2.32.1 compiled with -g with the normal gcc 421 from
> FreeBSD HEAD
>
I compiled ports/mail/evo-exchange 2.32.1 with
El día Tuesday, April 26, 2011 a las 04:16:56PM +0100, David Woodhouse escribió:
> On Tue, 2011-04-26 at 16:55 +0200, Matthias Apitz wrote:
> > I could entirely go back to 2.32.1 because the bug of the calendar stuff
> > is there as well... maybe this would help later to fix the 2.32.3 too;
> > Wh
On Tue, 2011-04-26 at 16:55 +0200, Matthias Apitz wrote:
> I could entirely go back to 2.32.1 because the bug of the calendar stuff
> is there as well... maybe this would help later to fix the 2.32.3 too;
> What do you think?
I don't think that'll make any difference at all.
There are no code ch
El día Tuesday, April 26, 2011 a las 03:17:52PM +0100, David Woodhouse escribió:
> >from
> > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackendexchange.so
> > #5 0x29f25368 in open_calendar () from
> > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackende
>
> OK
On Tue, 2011-04-26 at 15:52 +0200, Matthias Apitz wrote:
> Forget what I wrote about dbus and gnome-session-daemon; I tested this
> in a SSH session to the VM and not in the desktop itself; I'm so stupid
> sometime :-(
Heh. Easily done ;)
> Here is goes again:
> Program received signal SIGSEGV,
El día Tuesday, April 26, 2011 a las 01:38:11PM +0100, David Woodhouse escribió:
> On Tue, 2011-04-26 at 14:26 +0200, Matthias Apitz wrote:
> >
> > [guru@vm-9Current ~]$ dbus-monitor --session
> > Failed to open connection to session bus: /usr/local/bin/dbus-launch
> > terminated abnormally with
On Tue, 2011-04-26 at 14:26 +0200, Matthias Apitz wrote:
>
> [guru@vm-9Current ~]$ dbus-monitor --session
> Failed to open connection to session bus: /usr/local/bin/dbus-launch
> terminated abnormally with the following error: Autolaunch error: X11
> initialization failed.
OK, this is your proble
El día Tuesday, April 26, 2011 a las 01:10:52PM +0100, David Woodhouse escribió:
> On Tue, 2011-04-26 at 14:04 +0200, Matthias Apitz wrote:
> >
> > This is perhaps because:
> >
> > [guru@vm-9Current ~]$ /usr/local/libexec/gnome-settings-daemon
> >
> > ** (gnome-settings-daemon:2803): WARNING *
On Tue, 2011-04-26 at 14:04 +0200, Matthias Apitz wrote:
>
> This is perhaps because:
>
> [guru@vm-9Current ~]$ /usr/local/libexec/gnome-settings-daemon
>
> ** (gnome-settings-daemon:2803): WARNING **: Unable to initialize GTK+
I wonder if the real problem is that the DBus dæmon isn't
running/
El día Tuesday, April 26, 2011 a las 10:06:58AM +0100, David Woodhouse escribió:
> On Tue, 2011-04-26 at 08:32 +0200, Matthias Apitz wrote:
> > > OK. So please run e-calendar-factory from the command line, preferably
> > > in gdb, and show *its* output when you reproduce the original problem.
> >
On Tue, 2011-04-26 at 08:32 +0200, Matthias Apitz wrote:
> > OK. So please run e-calendar-factory from the command line, preferably
> > in gdb, and show *its* output when you reproduce the original problem.
>
> Just to make sure the procedure: do you want me to 1) start
> e-calendar-factory in gdb
El día Monday, April 25, 2011 a las 08:34:46PM +0100, David Woodhouse escribió:
> On Mon, 2011-04-25 at 16:23 +0200, Matthias Apitz wrote:
> > I have now compiled evolution-data-server 2.32.3 and (again)
> > evolution-2.32.3; the problem remains;
>
> OK. So please run e-calendar-factory from the
On Mon, 2011-04-25 at 16:23 +0200, Matthias Apitz wrote:
> I have now compiled evolution-data-server 2.32.3 and (again)
> evolution-2.32.3; the problem remains;
OK. So please run e-calendar-factory from the command line, preferably
in gdb, and show *its* output when you reproduce the original prob
El día Sunday, April 24, 2011 a las 08:33:59PM +0100, David Woodhouse escribió:
> On Sun, 2011-04-24 at 20:19 +0200, Matthias Apitz wrote:
> > El dÃa Sunday, April 24, 2011 a las 07:06:50PM +0100, David Woodhouse
> > escribió:
> > > Building evolution-2.32.3 requires evolution-data-server-2.32.
On Sun, 2011-04-24 at 20:19 +0200, Matthias Apitz wrote:
> El dÃa Sunday, April 24, 2011 a las 07:06:50PM +0100, David Woodhouse
> escribió:
> > Building evolution-2.32.3 requires evolution-data-server-2.32.3, but you
> > still seem to have e-d-s 2.32.1.
>
> Is this as well in the evolution-2.3
El dÃa Sunday, April 24, 2011 a las 07:06:50PM +0100, David Woodhouse
escribió:
> On Sun, 2011-04-24 at 18:05 +0200, Matthias Apitz wrote:
> > I've unpacked the source into /usr/ports/mail/evolution/work and renamed
> > the top level dir to .1; the patching to FreeBSD went (perhaps) fine but
>
On Sun, 2011-04-24 at 18:05 +0200, Matthias Apitz wrote:
> I've unpacked the source into /usr/ports/mail/evolution/work and renamed
> the top level dir to .1; the patching to FreeBSD went (perhaps) fine but
> the evo ./configure can't find its requirements, at least it is missing
> this:
Building
> - Forwarded message from David Woodhouse -
>
>
> On Sun, 2011-04-24 at 16:14 +0200, Matthias Apitz wrote:
> > It seems that 2.32.1 is the latest in the FreeBSD' ports? Is it possible
> > to compile it directly from the sources, and if so is there any guide
> > for this? Thanks
>
> Th
On Sun, 2011-04-24 at 16:14 +0200, Matthias Apitz wrote:
> It seems that 2.32.1 is the latest in the FreeBSD' ports? Is it possible
> to compile it directly from the sources, and if so is there any guide
> for this? Thanks
The differences should be so small that you ought to be able to just use
y
> - Forwarded message from David Woodhouse -
>
> Updating to 2.32.3 might be a good idea too, before going much further.
>
> --
> David WoodhouseOpen Source Technology Centre
> david.woodho...@intel.com Intel Corporation
>
I
On Sun, 2011-04-24 at 10:56 +0200, Matthias Apitz wrote:
>
>
> I have compiled FreeBSD and /usr/ports from CVS HEAD which brings Evo
> 2.32.1; Evo starts fine (if I don't count the kerberos message), but
> calendar ist not working, it gives only:
>
>
> ** (evolution:44013): WARNING **: Unexpect
Hello,
I have compiled FreeBSD and /usr/ports from CVS HEAD which brings Evo
2.32.1; Evo starts fine (if I don't count the kerberos message), but
calendar ist not working, it gives only:
** (evolution:44013): WARNING **: Unexpected kerberos error -1765328164
** (evolution:44013): WARNING **:
51 matches
Mail list logo
