> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Tom Lane
> Envoyé : jeudi 27 juillet 2006 19:26
> À : Daniel Caune
> Cc : pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
> Objet : Re: [SQL] PostgreSQL server terminated by signal 11
>
> "Daniel Caune" <[EMAIL PROTECTED]> writes:
> > I run the command responsible for creating the index and I entered
> "continue" in gdb for executing the command. After a while, the server
> crashes:
>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x08079e2a in slot_attisnull ()
> > (gdb)
> > Continuing.
>
> > Program terminated with signal SIGSEGV, Segmentation fault.
> > The program no longer exists.
>
> > I can't do "bt" since the program no longer exists.
>
> I think you typed one carriage return too many and the thing re-executed
> the last command, ie, the continue. Try it again.
>
OK, I'll try that tomorrow morning. Perhaps can I set a conditional breakpoint
to function slot_attisnull when parameter slot is null (or
slot->tts_tupleDescriptor is null).
> The lack of arguments shown for slot_attisnull suggests that all we're
> going to get is a list of function names, without line numbers or
> argument values. If that's not enough to figure out the problem, can
> you rebuild with --enable-debug to get a more useful stack trace?
>
Well, I installed PostgreSQL using apt-get but that won't be a problem to get
the source from the CVS repository and to build a postgres binary using the
option you provide to me. Just let me the time to do that. :-)
Thanks,
--
Daniel
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
