Re: segfault in recent snapshots

2013-03-07 Thread Henry S. Thompson
marco atzeri writes: > On 3/4/2013 5:20 PM, Christopher Faylor wrote: >> . .. >> But, Marco has already indicated that he knows about this issue. >> >> I don't think there is anything more that needs to be done here until >> Marco releases his new package. > > just uploaded a test version 9.2.3-1

Re: segfault in recent snapshots

2013-03-06 Thread marco atzeri
On 3/4/2013 5:20 PM, Christopher Faylor wrote: On Mon, Mar 04, 2013 at 02:17:35PM +0100, Corinna Vinschen wrote: Since you're running GDB anyway, what does `bt' print when the SEGV occured? It was already posted and it didn't make sense. http://cygwin.com/ml/cygwin/2013-03/msg00023.html That'

Re: segfault in recent snapshots

2013-03-04 Thread Christopher Faylor
On Mon, Mar 04, 2013 at 02:17:35PM +0100, Corinna Vinschen wrote: >Since you're running GDB anyway, what does `bt' print when the SEGV >occured? It was already posted and it didn't make sense. http://cygwin.com/ml/cygwin/2013-03/msg00023.html That's why I asked for the stackdump file since it exp

Re: segfault in recent snapshots

2013-03-04 Thread Corinna Vinschen
On Mar 4 13:21, Henry S. Thompson wrote: > Corinna Vinschen writes: > > > Since you're running GDB anyway, what does `bt' print when the SEGV > > occured? > >#0 0x003d in ?? () >#1 0x610fcf7c in pthread::init_mainthread () >at >/netrel/src/cygwin-snapshot-20130301-1/win

Re: segfault in recent snapshots

2013-03-04 Thread marco atzeri
On 3/4/2013 2:17 PM, Corinna Vinschen wrote: Since you're running GDB anyway, what does `bt' print when the SEGV occured? postgresql dll's allocation table are partially wrong, so they fail at load after a rebase. No clue why they survive 1.7.17 and fails on latest snapshots, I assume just p

Re: segfault in recent snapshots

2013-03-04 Thread Henry S. Thompson
marco atzeri writes: > I am only referring to postgresql, I know nothing about xemacs I understand -- just wondered if looking at the evidence I've posted you could see where the parallel might be. . . ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crich

Re: segfault in recent snapshots

2013-03-04 Thread marco atzeri
On 3/4/2013 2:20 PM, Henry S. Thompson wrote: marco atzeri writes: On 3/3/2013 1:02 PM, Henry S. Thompson wrote: Christopher Faylor writes: On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous thread?) "pr

Re: segfault in recent snapshots

2013-03-04 Thread Henry S. Thompson
Corinna Vinschen writes: > Since you're running GDB anyway, what does `bt' print when the SEGV > occured? #0 0x003d in ?? () #1 0x610fcf7c in pthread::init_mainthread () at /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/thread.cc:336 #2 0x61006cf5 in dll_crt0_1 ()

Re: segfault in recent snapshots

2013-03-04 Thread Henry S. Thompson
marco atzeri writes: > On 3/3/2013 1:02 PM, Henry S. Thompson wrote: >> Christopher Faylor writes: >> >>> On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous thread?) >>> >>> "previous thread"? >> >> htt

Re: segfault in recent snapshots

2013-03-04 Thread Corinna Vinschen
On Mar 4 12:36, Henry S. Thompson wrote: > Christopher Faylor writes: > > >>> And, if it is segfaulting then there is a stackdump file. > >>> Post that. > >> > >>Exception: STATUS_ACCESS_VIOLATION at eip=003D > >>eax=003D ebx= ecx=7792389A edx=006F017C esi=61006C50 > >>edi=0028CD

Re: segfault in recent snapshots

2013-03-04 Thread Henry S. Thompson
Christopher Faylor writes: >>> And, if it is segfaulting then there is a stackdump file. >>> Post that. >> >>Exception: STATUS_ACCESS_VIOLATION at eip=003D >>eax=003D ebx= ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78 >>ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe

Re: segfault in recent snapshots

2013-03-03 Thread Christopher Faylor
On Sun, Mar 03, 2013 at 12:02:43PM +, Henry S. Thompson wrote: >Christopher Faylor writes: > >> On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: >>>Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous >>>thread?) >> >> "previous thread"? > >http://cygwin.10696

Re: segfault in recent snapshots

2013-03-03 Thread marco atzeri
On 3/3/2013 1:02 PM, Henry S. Thompson wrote: Christopher Faylor writes: On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous thread?) "previous thread"? http://cygwin.1069669.n5.nabble.com/psql-crashes-wit

Re: segfault in recent snapshots

2013-03-03 Thread Henry S. Thompson
Christopher Faylor writes: > On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: >>Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous >>thread?) > > "previous thread"? http://cygwin.1069669.n5.nabble.com/psql-crashes-with-snapshot-td96270.html >>and locally comp

Re: segfault in recent snapshots

2013-03-02 Thread Christopher Faylor
On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: >Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous >thread?) "previous thread"? >and locally compiled xemacs. > >Any way I can help debug? Yes. As always, provide a simple test case which demonstrates the pro

Re: segfault in recent snapshots

2013-03-02 Thread Henry S. Thompson
I should have given two more bits of info: 1) Reverting to 1.7.17 cures the problem; 2) Loading cygwin1.dbg for the 2013-03-01 snapshot shows the following for psql: (gdb) bt #0 0x003d in ?? () #1 0x610fcf7c in pthread::init_mainthread () at /netrel/src/cygwin-snapsh

segfault in recent snapshots

2013-03-02 Thread Henry S. Thompson
Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous thread?) and locally compiled xemacs. Any way I can help debug? ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440