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

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

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pghackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Server process exited with status 139 (meaning?)
Date: 2000-06-26 05:25:10
Message-ID: 3956E936.E87CA36D@austin.rr.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> 
> Ed Loehr <eloehr(at)austin(dot)rr(dot)com> writes:
> > I don't need help on this as I found workable queries for my purposes,
> > but here is a simplified core-dumper (7.0beta3) for posterity...
> 
> This doesn't come close to doing anything as-is, but even reading
> between the lines ("activity"=>"bar" etc) and deleting references
> to missing fields, I can't get a crash.  Possibly a bug fixed since
> beta3?

I'll assume you tried my latest typo-free version on an HP box after
posting this and got the same results (i.e., nothing).  Maybe someone
else would care to verify on a Linux box?  I'm on RH 6.2 with dual
PIII's...

Regards,
Ed Loehr

In response to

Responses

pgsql-hackers by date

Next:From: Ed LoehrDate: 2000-06-26 05:29:37
Subject: Re: ExecInitIndexScan: both left and right ops are rel-vars
Previous:From: Ed LoehrDate: 2000-06-26 05:14:35
Subject: ExecInitIndexScan: both left and right ops are rel-vars

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