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

Re: Server process exited with status 139 (meaning?)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
Cc: pghackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Server process exited with status 139 (meaning?)
Date: 2000-06-25 01:01:18
Message-ID: Pine.LNX.4.21.0006241904051.348-100000@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackers
Ed Loehr writes:

> I have a query crashing the backend and leaving this message in the
> server log...
> What does exit status 139 mean?

The backend terminated because of a segmentation fault (note 139 = 128 +
11, 11 = SIGSEGV). So it's definitely a bug and we'd need to see the
query.

> Better still would be a pointer to some documentation for error codes
> if such beast exists...

See wait(2). Of course we could also make the error message more
expressive.

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-06-25 01:59:58
Subject: Re: 64-bit sequences
Previous:From: Peter EisentrautDate: 2000-06-25 01:00:51
Subject: Re: Big 7.1 open items

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group