Re: Is *that* why debugging backend startup is so hard!?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is *that* why debugging backend startup is so hard!?
Date: 2000-06-27 03:47:33
Message-ID: 200006270347.XAA04616@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Needless to say I find this braindead in the extreme. Will anyone
> object if I change the signal masks so that we never ever block
> SIGABRT, SIGILL, SIGSEGV, SIGBUS, SIGTRAP, SIGCONT, SIGSYS? Any
> other candidates? Are there any systems that do not define all
> of these signal names?
>
> BTW, once I turned this silliness off, I was able to home in on
> my bug within minutes...

Go ahead. Current setup sound very broken. Why do they even bother
doing all this. Seems we should identify the signals we want to block,
and just block those.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-06-27 04:07:28 Re: Big 7.1 open items
Previous Message Thomas Lockhart 2000-06-27 02:41:18 SQL99 functions