Mark Wong wrote:
> Hi everyone,
> I was playing with converting unixtop (the version of top used in
> FreeBSD) to only show PostgreSQL processes pulled from the
> pg_stat_activity table. I have a version that kind of works here:
Nice idea. But I got a segfault trying to execute it. My SO is a
Slackware 12.0, glibc 2.5, gcc 4.1.2. I didn't have time to look through
the code, sorry.
euler(at)harman:~/Desktop/ptop-3.6.1-pre6$ gdb ./ptop
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
Starting program: /home/euler/Desktop/ptop-3.6.1-pre6/ptop
[Thread debugging using libthread_db enabled]
[New Thread -1212918080 (LWP 9600)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212918080 (LWP 9600)]
0xb7e8e8c0 in __find_specmb () from /lib/libc.so.6
#0 0xb7e8e8c0 in __find_specmb () from /lib/libc.so.6
#1 0xb7e757ff in vfprintf () from /lib/libc.so.6
#2 0xb7e97d91 in vsnprintf () from /lib/libc.so.6
#3 0x0804cd8c in new_message_v (type=3,
msgfmt=0x96c73ac3 <Address 0x96c73ac3 out of bounds>,
ap=0xbfbae324 "Èt\a\b \003»¿6]ñ·¼ý·t£ý·Hãº¿t£ý·\224\003»¿")
#4 0x0804ced2 in error_message (
msgfmt=0x96c73ac3 <Address 0x96c73ac3 out of bounds>) at display.c:1392
#5 0xb7fc2c79 in ?? () from /usr/lib/libpq.so.5
#6 0x96c73ac3 in ?? ()
#7 0x080774c8 in ?? ()
#8 0xbfbb03a0 in ?? ()
#9 0xb7f15d36 in pthread_mutex_lock () from /lib/libc.so.6
#10 0xb7fc2d49 in ?? () from /usr/lib/libpq.so.5
#11 0x00000001 in ?? ()
#12 0x00000000 in ?? ()
Euler Taveira de Oliveira
In response to
pgsql-hackers by date
|Next:||From: Neil Conway||Date: 2007-09-26 03:36:27|
|Subject: Re: plpgsql TABLE patch|
|Previous:||From: Tom Lane||Date: 2007-09-26 02:15:28|
|Subject: Re: plpgsql TABLE patch |