search for: datastack_pool

Displaying 8 results from an estimated 8 matches for "datastack_pool".

2005 Sep 09
1
1.0alpha1: stack frame core
...c = 0x70244 <pool_data_stack_malloc>, free = 0x70290 <pool_data_stack_free>, realloc = 0x702bc <pool_data_stack_realloc>, clear = 0x7036c <pool_data_stack_clear>, get_max_easy_alloc_size = 0x70374 <pool_data_stack_get_max_easy_alloc_size>, alloconly_pool = 1, datastack_pool = 1} (gdb) print dpool No symbol "dpool" in current context. (gdb) down #4 0x00070304 in pool_data_stack_realloc (pool=Variable "pool" is not available. ) at mempool-datastack.c:112 112 i_panic("pool_data_stack_realloc(): stack frame changed"); (gd...
2010 Jun 14
1
v2.0.beta6 compilation problem under Solaris 9
...match.o "imap-match.c", line 195: warning: syntax error: empty declaration "imap-match.c", line 199: identifier redeclared: imap_match_dup current : function(pointer to struct pool {pointer to const struct pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int datastack_pool :1}, pointer to const struct imap_match_glob {pointer to struct pool {..} pool, pointer to struct imap_match_pattern {..} patterns, char sep, array[-1] of char patterns_data}) returning pointer to struct imap_match_glob {pointer to struct pool {..} pool, pointer to struct imap_match_pattern {..} pa...
2004 Dec 20
1
panic with search
...%"PRIuSIZE_T" bytes", new_size); 108 109 if (dpool->data_stack_frame != data_stack_frame) 110 i_panic("pool_data_stack_realloc(): stack frame changed"); 111 112 if (mem == NULL) 113 return pool_data_stack_malloc(pool, new_size); 114 (gdb) p dpool $18 = (struct datastack_pool *) 0x80c7788 (gdb) p *dpool $19 = {pool = {get_name = 0x80afbd5 <pool_data_stack_get_name>, ref = 0x80afbdf <pool_data_stack_ref>, unref = 0x80afc0d <pool_data_stack_unref>, malloc = 0x80afc70 <pool_data_stack_malloc>, free = 0x80afcc4 <pool_data_stack_free>,...
2015 Apr 08
2
dovecot-2.2.16 compilation problems under Solaris Studio 11
...8plusa -I/opt/local/include -c imap-match.c -KPIC -DPIC -o .libs/imap-match.o "imap-match.c", line 199: identifier redeclared: imap_match_dup current : function(pointer to struct pool {pointer to const struct pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int datastack_pool :1}, pointer to const struct imap_match_glob {pointer to struct pool {..} pool, pointer to struct imap_match_pattern {..} patterns, char sep, array[-1] of char patterns_data}) returning pointer to struct imap_match_glob {pointer to struct pool {..} pool, pointer to struct imap_match_pattern...
2008 Jun 13
2
configure error on HP-UX: C99 compatible vsnprintf() call
Hi All, I tried to build dovecot-1.1.rc9 on a HP-UX machine, but failed to configure with the following message: configure: error: You don't appear to have C99 compatible vsnprintf() call The environment is like the following: - command: ./configure - uname: HP-UX B.11.23 U ia64 - aCC version: HP aC++/ANSI C B3910B A.05.55 [Dec 04 2003] Also, I tried to run `./configure CC=c99'
2005 Mar 22
2
Address with whitespace shows as ""@MISSING_DOMAIN
It seems that Dovecot gets confused when presented with a header like: From: someone at somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE
2010 Aug 16
19
v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0
2010 Aug 16
19
v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0