On 2/19/2013 6:51 AM, marco atzeri wrote:
From a DOS prompt:
psql --version
1 [main] psql 3196 exception::handle: Exception: STATUS_ACCESS_VIOLATION
626 [main] psql 3196 open_stackdumpfile: Dumping stack trace to
psql.exe.stackdump
And from a bash prompt:
$ psql --version
Segmentation faul
On 2/18/2013 8:44 PM, Thorsten Kampe wrote:
* Christopher Faylor (Mon, 18 Feb 2013 10:46:43 -0500)
On Mon, Feb 18, 2013 at 04:27:17PM +0100, Thorsten Kampe wrote:
I just downloaded the PostgreSQL client tools and noticed that psql
crashes every time. The usual rebase didn't help. I reverted cyg
Thorsten Kampe writes:
> What can I do - if anything at all - to debug the issue? Obviously, I
> cannot test every single snapshot after October last year and see where
> the crash "starts"...
If the problem is bisectable it would take no more than 5 snapshots to
get the one that has the respons
On Mon, Feb 18, 2013 at 04:27:17PM +0100, Thorsten Kampe wrote:
>Hello,
>
>I just downloaded the PostgreSQL client tools and noticed that psql
>crashes every time. The usual rebase didn't help. I reverted cygwin1.dll
>to the latest official version (1.7.17, 2012-10-19) and now psql works
>fine.
On Mon, Feb 18, 2013 at 10:27 AM, Thorsten Kampe wrote:
> What can I do - if anything at all - to debug the issue? Obviously, I
> cannot test every single snapshot after October last year and see where
> the crash "starts"...
Work it descending order with a set number limit.
--
Earnie
-- https:/
5 matches
Mail list logo