No, it isn't a debug-enabled build, and I don't think the debug symbols
package is installed on that system. I've never used GDB, I'm more of an
'applications' programmer, I may need a 'crash' course on it, if you pardon
the pun. However, if it's anything like the debugging tools I used to use
w
Michael Nolan escribió:
> GDB produces:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0804fd6f in dumpSequence ()
Not very helpful -- what does it say if you ask for "bt"? I'm thinking
this is not a debug-enabled build though. I think you have to install a
separate RPM package in
GDB produces:
Program received signal SIGSEGV, Segmentation fault.
0x0804fd6f in dumpSequence ()
The sequence definitely exists and works:
select * from uscf_dues_dues_key_seq
;
sequence_name | last_value | increment_by | max_value |
min_
value | cache_value | log_cnt | is_cy
Michael Nolan escribió:
> /usr/local/pgsql/bin/pg_dump -v
> -t uscf_dues_dues_key_seq -U postgres uscf >uscf_dues_dues_key_seq.seq
>
> Any ideas what to try?
Here's one: get a backtrace from GDB. Here, I get this error:
$ LC_ALL=C pg_dump -v -t uscf_dues_dues_key_seq -U alvherre uscf
pg_dump:
I get a segmentation fault in pg_dump (8.2.3 on a Linux Fedora Core 5
system) when dumping some (but not all) of the sequences in the public
schema:.
Here's the output from /usr/local/pgsql/bin/pg_dump -v -t
uscf_dues_dues_key_seq -U postgres uscf >uscf_dues_dues_key_seq.seq
pg_dump: reading sch
