[pgpool-general: 9114] Re: Another segmentation fault

[Tatsuo Ishii]

> No worries. I hope you had a good trip. Last night we triggered the last
> crash again. Is there anything we can do to make it easier for you to find
> the cause?

It would be helpful if you could share some variable values in the
core file. Since I don't have the pgpool load module when you got the
core, I cannot inspect the variables using the core you provided.

> #0  connect_backend (sp=0x55803eb0a6b8, frontend=0x55803eb08768) at
> protocol/child.c:1076
> #1  0x000055803ce3d02a in get_backend_connection (frontend=0x55803eb08768)
> at protocol/child.c:2112
> #2  0x000055803ce38fd5 in do_child (fds=0x55803eabea90) at
> protocol/child.c:416
> #3  0x000055803cdfea4c in fork_a_child (fds=0x55803eabea90, id=13) at
> main/pgpool_main.c:863
> #4  0x000055803cdfde30 in PgpoolMain (discard_status=0 '\000',
> clear_memcache_oidmaps=0 '\000') at main/pgpool_main.c:561
> #5  0x000055803cdfb9e6 in main (argc=2, argv=0x7ffc8cdddda8) at
> main/main.c:365

Around protocol/child.c:1076:
				/* set DB node id */
				pool_set_db_node_id(CONNECTION(backend, i), i);

I want to see the values in the "backend" struct. Since CONNECTION
macro is used here, you have to do something like in a gdb session.

p *backend->slots[0]
p *backend->slots[1]
p *backend->slots[2]

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp