Unix Technical Forum

Weird psql crash

This is a discussion on Weird psql crash within the pgsql Hackers forums, part of the PostgreSQL category; --> Hi, 1. Fire up psql. 2. Press Ctrl-4 3. Crash, core dump... Chris ---------------------------(end of broadcast)--------------------------- TIP 7: don't ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Hackers

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-11-2008, 03:21 AM
Christopher Kings-Lynne
 
Posts: n/a
Default Weird psql crash

Hi,

1. Fire up psql.
2. Press Ctrl-4
3. Crash, core dump...

Chris

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-11-2008, 03:21 AM
Tom Lane
 
Posts: n/a
Default Re: Weird psql crash

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> 1. Fire up psql.
> 2. Press Ctrl-4
> 3. Crash, core dump...


SIGQUIT is supposed to do that.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 04-11-2008, 03:21 AM
Christopher Kings-Lynne
 
Posts: n/a
Default Re: Weird psql crash

>>1. Fire up psql.
>>2. Press Ctrl-4
>>3. Crash, core dump...

>
>
> SIGQUIT is supposed to do that.


Seems to be a libreadline thing:

#0 0x2827fd60 in sigprocmask () from /usr/lib/libc.so.4
#1 0x281f5adb in _rl_savestring () from /usr/lib/libreadline.so.4
#2 0xbfbfffac in ?? ()
#3 0x281f2254 in rl_read_key () from /usr/lib/libreadline.so.4
#4 0x28202e20 in readline_internal_char () from /usr/lib/libreadline.so.4
#5 0x28202f79 in readline_internal_char () from /usr/lib/libreadline.so.4
#6 0x28202fa9 in readline_internal_char () from /usr/lib/libreadline.so.4
#7 0x28202b70 in readline () from /usr/lib/libreadline.so.4
#8 0x804ee9c in gets_interactive (prompt=0x8074a00 "test=# ") at input.c:95
#9 0x804f702 in MainLoop (source=0x282ce0c0) at mainloop.c:153
#10 0x8051310 in main (argc=2, argv=0xbfbffc04) at startup.c:314

Chris

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 04-11-2008, 03:21 AM
Tom Lane
 
Posts: n/a
Default Re: Weird psql crash

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
>> SIGQUIT is supposed to do that.


> Seems to be a libreadline thing:


No, it's a built-in thing. See "man stty", "man tty(4)", "man termio"
or related topics depending on your platform. The point is that the
kernel terminal driver takes that as a command to send SIGQUIT to your
program, not much different from mapping control-C to SIGINT for
example. And the default handling for SIGQUIT is stop+dump core.

It's a feature, not a bug.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 11:32 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com