Autor: Phil Pennock Data: Para: Pawel Rutkowski CC: exim-users Asunto: Re: [exim] General protection error
On 2011-09-11 at 07:16 +0200, Pawel Rutkowski wrote: > Hello,
>
> > Else:
> >
> > Configure your system to permit setuid programs to dump core; set
> > rlimits accordingly; grab coredump, run:
> > $ gdb /path/to/exim /path/to/exim.core
> > and issue the "bt" command, which will tell you where it died, and
> > suggest which library it was in.
> >
>
> I try version with coredump. Run:
Did you do the version comparison of the libraries, as suggested?
> (gdb) bt
> #0 0x000000000046b660 in smtp_read_response ()
> #1 0x0000000000491950 in smtp_deliver ()
> #2 0x000000000049451e in smtp_transport_entry ()
> #3 0x00000000004232c1 in do_remote_deliveries ()
> #4 0x00000000004265ea in deliver_message ()
> #5 0x000000000042f884 in main ()
That's ... rather worrying to see in a backtrace; smtp_read_response()
is very well-used code and we shouldn't be seeing surprises there.
Any chance that you could compile Exim with debug information (-ggdb)
and _not_ strip it, so we can see more information in the backtrace?