Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: [SQL] PostgreSQL server terminated by signal 11



"Daniel Caune" <daniel(dot)caune(at)ubisoft(dot)com> 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.

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?

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group