pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped - Mailing list pgsql-hackers

From tushar
Subject pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped
Date
Msg-id CAC6VRobi3BEuFM-Yjr=VteyWh4tvs_tnL10KGsCzthZsfw7TSQ@mail.gmail.com
Whole thread Raw
Responses Re: pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped
Re: pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped
List pgsql-hackers
Hi,
I found a scenario where, after firing the  wrong way of using the pg_dump command, not only server fail to start, 
But  later, I am not able to perform initdb/pg_ctl  as well 

Please refer to this testcase:
"
PG v19 devel, Cluster running on default port=5432 
Run pg_dump (./pg_dump -Ft -s -c   -v -f postgres schema_clean.tar1)
"

The result is :
edb@1a1c15437e7c bin]$ ./pg_dump -Ft -s -c   -v -f postgres schema_clean.tar1
qemu: uncaught target signal 7 (Bus error) - core dumped
qemu-x86_64:qemu-x86_64:qemu-x86_64:  QEMU internal SIGBUS {code=ADRERR, addr=0x8c6b70}QEMU internal SIGBUS {code=ADRERR, addr=0x8c6b70}
QEMU internal SIGBUS {code=ADRERR, addr=0x8c6b70}
qemu-x86_64:qemu-x86_64:  QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
qemu-x86_64: QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
qemu-x86_64:qemu-x86_64: QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
 QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
pg_dump: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

 The correct way is to use 
./pg_dump -Ft -s -c   -v -f  schema_clean.tar1 postgres 

Is there any way we can generate some error messages?

regards,

pgsql-hackers by date:

Previous
From: tushar
Date:
Subject: Re: Non-text mode for pg_dumpall
Next
From: Heikki Linnakangas
Date:
Subject: Re: Moving _bt_readpage and _bt_checkkeys into a new .c file