postfix-users October 2010 archive
Main Archive Page > Month Archives  > postfix-users archives
postfix-users: Re: postscreen segfault

Re: postscreen segfault

From: Vernon A. Fort <vfort_at_nospam>
Date: Wed Oct 06 2010 - 17:51:16 GMT
To: postfix-users@postfix.org

On Wed, 2010-10-06 at 13:37 -0400, Victor Duchovni wrote:
> On Wed, Oct 06, 2010 at 12:28:45PM -0500, Vernon A. Fort wrote:
>
> > > We don't yet need the whole core file, just run:
> > >
> > > gdb /usr/sbin/postscreen /path/to/core
> > > ... copious output ...
> > > gdb) bt
> > >
> > > The "bt" command generates a back-trace (stack trace), that should show
> > > where the segfault occurred. Ideally, your postscreen is compiled with
> > > "-g" or "-g -O", i.e. with symbols and line numbers, ...
> > >
> >
> > attached. This is a gentoo install so added the "ggdb" flag to the
> > make.conf file and re-compiled postfix. I also removed the
> > -fomit-frame-pointer per the backtrace doc's.
>
> Sadly, the binary still has no symbols. It should be compiled with
> "-g" or "-g -O" and installed without being stripped, although that
> is not too hard to fix, by running gdb on the unstripped binary
> in the build-tree instead.
>
> > This is my first time working with core and backtrace files - bear with
> > me.
>
> Thanks. This is closer, but the "postscreen" binary does not yet have
> the necessary symbol table.
>

I recompiled postfix: unstripped and with -ggdb. I ran gdb postscreen
core file - new binary but old core file. May be still useful but will
have to wait on another segfault.

attached is the backtrace using new binary with old core file.

Vernon