Hello!
Today i discovered another strange bug.
Since i have started with dbmail i'm running it under solaris running with
sparc processors. Today i wanted to test dbmail on intel based solaris box.
And i discovered new problems. It's really strange.
Below you will find the output from the sparc
Lars Kneschke <[EMAIL PROTECTED]> schrieb:
>Hello!
>
>Today i discovered another strange bug.
I got i narrowed down to this piece of code:
int dbmail_imap_session_printf(struct ImapSession * self, char * message,
...)
trace(TRACE_MESSAGE, "%s,%s: A string: %s", __FILE__, __func__,
messa
On Fri, 2006-06-23 at 12:12 +0200, Lars Kneschke wrote:
> Lars Kneschke <[EMAIL PROTECTED]> schrieb:
> >Hello!
> >
> >Today i discovered another strange bug.
>
> I got i narrowed down to this piece of code:
>
> int dbmail_imap_session_printf(struct ImapSession * self, char * message,
> ...)
>
>
Aaron Stone <[EMAIL PROTECTED]> schrieb:
>In your glib builds, look to see if one or both are using the Solaris
>libc's vasnprintf, or if they're using the Gnulib vasnprintf.
I also tracked it down to this point. But currently i'm missing some
knowledge, but find out which implementation is used.
On Fri, 2006-06-23 at 22:24 +0200, Lars Kneschke wrote:
> Aaron Stone <[EMAIL PROTECTED]> schrieb:
> >In your glib builds, look to see if one or both are using the Solaris
> >libc's vasnprintf, or if they're using the Gnulib vasnprintf.
>
> I also tracked it down to this point. But currently i'm
Am Freitag, 23. Juni 2006 23:31 schrieb Aaron Stone:
> Ok, let us know if you need any help!
Aaron Stone <[EMAIL PROTECTED]> schrieb:
>
>Ok, let us know if you need any help!
I'm lost...
Jun 25 22:44:24 comp-isol01.metaways.net dbmail/imap4d[2283]: [ID 748625
mail.notice] Info COMMAND: [0001