public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* segfault in recent snapshots
@ 2013-03-02 20:00 Henry S. Thompson
  2013-03-02 20:25 ` Henry S. Thompson
  2013-03-02 20:29 ` Christopher Faylor
  0 siblings, 2 replies; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-02 20:00 UTC (permalink / raw)
  To: cygwin

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
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-02 20:00 segfault in recent snapshots Henry S. Thompson
@ 2013-03-02 20:25 ` Henry S. Thompson
  2013-03-02 20:29 ` Christopher Faylor
  1 sibling, 0 replies; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-02 20:25 UTC (permalink / raw)
  To: cygwin

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  0x003d0000 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 ()
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/dcrt0.cc:861
   #3  0x6100537d in _cygtls::call2 (this=<optimized out>,
       func=0x61006c50 <dll_crt0_1(void*)>, arg=0x0,
       buf=0x6100551b <_cygtls::call(unsigned long (*)(void*, void*),
   void*)+91>)
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/cygtls.cc:99
   #4  0x0028ff48 in ?? ()
   #5  0x004330c2 in ?? ()
   #6  0x00401015 in ?? ()
   #7  0x752633aa in KERNEL32!BaseCleanupAppcompatCacheSupport ()
      from /c/Windows/syswow64/kernel32.dll
   #8  0x0028ffd4 in ?? ()
   #9  0x77929ef2 in ntdll!RtlpNtSetValueKey () from
   /c/Windows/system32/ntdll.dll
   #10 0xfffde000 in ?? ()
   #11 0x77929ec5 in ntdll!RtlpNtSetValueKey () from
   /c/Windows/system32/ntdll.dll
   #12 0x00401000 in ?? ()
   #13 0x00000000 in ?? ()

and the following for xemacs:

   #0  0x003d0000 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 ()
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/dcrt0.cc:861
   #3  0x6100537d in _cygtls::call2 (this=<optimized out>,
       func=0x61006c50 <dll_crt0_1(void*)>, arg=0x0,
       buf=0x6100551b <_cygtls::call(unsigned long (*)(void*, void*),
   void*)+91>)
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/cygtls.cc:99
   #4  0x0028ff48 in ?? ()
   #5  0x00641572 in cygwin_crt0 (f=0x458b7f <main>)
       at
   /usr/src/debug/cygwin-1.7.17-1/winsup/cygwin/lib/cygwin_crt0.c:22
   #6  0x00401015 in mainCRTStartup ()
       at /usr/src/debug/cygwin-1.7.17-1/winsup/cygwin/crt0.c:29

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-02 20:00 segfault in recent snapshots Henry S. Thompson
  2013-03-02 20:25 ` Henry S. Thompson
@ 2013-03-02 20:29 ` Christopher Faylor
  2013-03-03 12:02   ` Henry S. Thompson
  1 sibling, 1 reply; 17+ messages in thread
From: Christopher Faylor @ 2013-03-02 20:29 UTC (permalink / raw)
  To: cygwin

On Sat, Mar 02, 2013 at 08:00:38PM +0000, 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
problem.  And, if it is segfaulting then there is a stackdump file.
Post that.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-02 20:29 ` Christopher Faylor
@ 2013-03-03 12:02   ` Henry S. Thompson
  2013-03-03 16:18     ` marco atzeri
  2013-03-03 18:06     ` Christopher Faylor
  0 siblings, 2 replies; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-03 12:02 UTC (permalink / raw)
  To: cygwin

Christopher Faylor writes:

> On Sat, Mar 02, 2013 at 08:00:38PM +0000, 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 compiled xemacs.
>>
>>Any way I can help debug?
>
> Yes.  As always, provide a simple test case which demonstrates the
> problem.

Sigh, not within my competence in this case.

> And, if it is segfaulting then there is a stackdump file.
> Post that.

Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
eax=003D0000 ebx=00000000 ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78
ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe, pid 11572, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args
0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
End of stack trace

Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
eax=003D0000 ebx=00000000 ecx=7792389A edx=0112017C esi=61006C50 edi=0028CD78
ebp=0028AC88 esp=0028AC4C program=C:\cygwin\usr\local\bin\xemacs-21.5-b33.exe, pid 10904, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args
0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
End of stack trace

I think there's probably more detail in the gdb stacktraces I posted
subsequently. . .

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-03 12:02   ` Henry S. Thompson
@ 2013-03-03 16:18     ` marco atzeri
  2013-03-04 13:21       ` Henry S. Thompson
  2013-03-03 18:06     ` Christopher Faylor
  1 sibling, 1 reply; 17+ messages in thread
From: marco atzeri @ 2013-03-03 16:18 UTC (permalink / raw)
  To: cygwin

On 3/3/2013 1:02 PM, Henry S. Thompson wrote:
> Christopher Faylor writes:
>
>> On Sat, Mar 02, 2013 at 08:00:38PM +0000, 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 compiled xemacs.
>>>
>>> Any way I can help debug?
>>
>> Yes.  As always, provide a simple test case which demonstrates the
>> problem.
>
> Sigh, not within my competence in this case.
>
>> And, if it is segfaulting then there is a stackdump file.
>> Post that.
>
[cut]
>
> I think there's probably more detail in the gdb stacktraces I posted
> subsequently. . .
>
> ht
>

Henry,
I am aware of the issue on postgresql, and working on a real solution,
plus a workaround for short term.

It is due to bad dll's built by "dlltool+dllwrap" that crash
after rebase and the only real solution seems to switch
on "gcc -shared"

Regards
Marco





--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-03 12:02   ` Henry S. Thompson
  2013-03-03 16:18     ` marco atzeri
@ 2013-03-03 18:06     ` Christopher Faylor
  2013-03-04 12:37       ` Henry S. Thompson
  1 sibling, 1 reply; 17+ messages in thread
From: Christopher Faylor @ 2013-03-03 18:06 UTC (permalink / raw)
  To: cygwin

On Sun, Mar 03, 2013 at 12:02:43PM +0000, Henry S. Thompson wrote:
>Christopher Faylor writes:
>
>> On Sat, Mar 02, 2013 at 08:00:38PM +0000, 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

That's the thread where Marco said:

"strangely I noticed that psql of 9.2.2-1 does not suffer this problem,
and it seems due to cygpq.dll (rebase address ?)."

i.e., not a Cygwin snapshot problem.

>>>and locally compiled xemacs.
>>>
>>>Any way I can help debug?
>>
>> Yes.  As always, provide a simple test case which demonstrates the
>> problem.
>
>Sigh, not within my competence in this case.
>
>> And, if it is segfaulting then there is a stackdump file.
>> Post that.
>
>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
>eax=003D0000 ebx=00000000 ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78
>ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe, pid 11572, thread main
>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>Stack trace:
>Frame     Function  Args
>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
>End of stack trace
>
>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
>eax=003D0000 ebx=00000000 ecx=7792389A edx=0112017C esi=61006C50 edi=0028CD78
>ebp=0028AC88 esp=0028AC4C program=C:\cygwin\usr\local\bin\xemacs-21.5-b33.exe, pid 10904, thread main
>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>Stack trace:
>Frame     Function  Args
>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
>End of stack trace
>
>I think there's probably more detail in the gdb stacktraces I posted
>subsequently. . .

The 003D0000 was in your gdb stacktrace but there is more useful detail,
and less superfluous cruft above.

This address indicates that the error is in user code, so this again
devolves to something that Marco would likely have to look into.  The
"003D0000" looks like a DLL which has not been properly rebased.

If you can duplicate this under gdb then "info shared" should tell you
which dll is associated with that address.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-03 18:06     ` Christopher Faylor
@ 2013-03-04 12:37       ` Henry S. Thompson
  2013-03-04 13:17         ` Corinna Vinschen
  0 siblings, 1 reply; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-04 12:37 UTC (permalink / raw)
  To: cygwin

Christopher Faylor writes:

>>> And, if it is segfaulting then there is a stackdump file.
>>> Post that.
>>
>>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
>>eax=003D0000 ebx=00000000 ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78
>>ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe, pid 11572, thread main
>>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>>Stack trace:
>>Frame     Function  Args
>>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
>>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
>>End of stack trace
>>
>>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
>>eax=003D0000 ebx=00000000 ecx=7792389A edx=0112017C esi=61006C50 edi=0028CD78
>>ebp=0028AC88 esp=0028AC4C program=C:\cygwin\usr\local\bin\xemacs-21.5-b33.exe, pid 10904, thread main
>>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>>Stack trace:
>>Frame     Function  Args
>>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
>>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
>>End of stack trace
>>
>
> This address indicates that the error is in user code, so this again
> devolves to something that Marco would likely have to look into.  The
> "003D0000" looks like a DLL which has not been properly rebased.
>
> If you can duplicate this under gdb then "info shared" should tell you
> which dll is associated with that address.

Sorry if I've not understood correctly, but when I catch the segfault
in gdb, info shared doesn't show anything loaded in that address
range:

(gdb) info shared
From        To          Syms Read   Shared Object Library
0x778f1000  0x77a55d1c  Yes (*)     /c/Windows/system32/ntdll.dll
0x75251000  0x7534bd58  Yes (*)     /c/Windows/syswow64/kernel32.dll
0x76581000  0x765c6a18  Yes (*)     /c/Windows/syswow64/KERNELBASE.dll
0x61001000  0x61480000  Yes         /c/Cygwin/bin/cygwin1.dll
0x6da81000  0x6db6cac8  Yes (*)     /c/Cygwin/bin/cygdb-4.5.dll
0x6b0b1000  0x6b0b60e4  Yes (*)     /c/Cygwin/bin/cyggdbm_compat-4.dll
0x6b0e1000  0x6b0ea168  Yes (*)     /c/Cygwin/bin/cyggdbm-4.dll
0x683a1000  0x683d6748  Yes (*)     /c/Cygwin/bin/cygjpeg-8.dll
0x6d541000  0x6d5575b4  Yes (*)     /c/Cygwin/bin/cyggcc_s-1.dll
0x67861000  0x67894e00  Yes (*)     /c/Cygwin/bin/cygncurses-10.dll
0x65e01000  0x65e27018  Yes (*)     /c/Cygwin/bin/cygpng15-15.dll
0x64fc1000  0x64fd63c0  Yes (*)     /c/Cygwin/bin/cygz.dll
0x67d11000  0x67d33c60  Yes (*)     /c/Cygwin/bin/cygpq.dll
0x6dcb1000  0x6de3301c  Yes (*)     /c/Cygwin/bin/cygcrypto-1.0.0.dll
0x684c1000  0x684ce508  Yes (*)     /c/Cygwin/bin/cygintl-8.dll
0x69b41000  0x69c3bdcc  Yes (*)     /c/Cygwin/bin/cygiconv-2.dll
0x68071000  0x680b301c  Yes (*)     /c/Cygwin/bin/cygldap_r-2-4-2.dll
0x68211000  0x6821f01c  Yes (*)     /c/Cygwin/bin/cyglber-2-4-2.dll
0x67c61000  0x67c7aafc  Yes (*)     /c/Cygwin/bin/cygsasl2-2.dll
0x65581000  0x655e101c  Yes (*)     /c/Cygwin/bin/cygssl-1.0.0.dll
0x6fcd1000  0x6fcdf430  Yes (*)     /c/Cygwin/bin/cygXpm-noX-4.dll
0x76eb1000  0x76f2292c  Yes (*)     /c/Windows/syswow64/GDI32.dll
0x769c1000  0x76aa4198  Yes (*)     /c/Windows/syswow64/USER32.dll
0x76ac1000  0x76b5f04c  Yes (*)     /c/Windows/syswow64/ADVAPI32.dll
0x76631000  0x766db2c4  Yes (*)     /c/Windows/syswow64/msvcrt.dll
0x76801000  0x76818ed8  Yes (*)     /c/Windows/SysWOW64/sechost.dll
0x76f41000  0x77015e04  Yes (*)     /c/Windows/syswow64/RPCRT4.dll
0x74fd1000  0x750121f0  Yes (*)     /c/Windows/syswow64/SspiCli.dll
0x74fc1000  0x74fcb474  Yes (*)     /c/Windows/syswow64/CRYPTBASE.dll
0x75651000  0x756592f8  Yes (*)     /c/Windows/syswow64/LPK.dll
0x76df1000  0x76e8c9fc  Yes (*)     /c/Windows/syswow64/USP10.dll
0x718e1000  0x71963f0c  Yes (*)     /c/Windows/WinSxS/x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af/COMCTL32.DLL
0x75661000  0x756da39c  Yes (*)     /c/Windows/syswow64/COMDLG32.DLL
0x755f1000  0x75646b60  Yes (*)     /c/Windows/syswow64/SHLWAPI.dll
0x75841000  0x76489898  Yes (*)     /c/Windows/syswow64/SHELL32.dll
0x76521000  0x76561ce0  Yes (*)     /c/Windows/syswow64/IMM32.DLL
0x76b61000  0x76c2bebc  Yes (*)     /c/Windows/syswow64/MSCTF.dll
0x70261000  0x702719d4  Yes (*)     /c/Windows/SysWOW64/MPR.DLL
0x756e1000  0x7583b0cc  Yes (*)     /c/Windows/syswow64/ole32.dll
0x72b91000  0x72bc1264  Yes (*)     /c/Windows/SysWOW64/WINMM.DLL
0x70281000  0x702d07a0  Yes (*)     /c/Windows/SysWOW64/WINSPOOL.DRV
0x73461000  0x734ab464  Yes (*)     /c/Windows/SysWOW64/apphelp.dll
0x6d001000  0x6d08c524  Yes (*)     /c/Windows/AppPatch/AcLayers.DLL
0x76491000  0x7651e644  Yes (*)     /c/Windows/syswow64/OLEAUT32.dll
0x73371000  0x73386f9c  Yes (*)     /c/Windows/SysWOW64/USERENV.dll
0x749a1000  0x749aa440  Yes (*)     /c/Windows/SysWOW64/profapi.dll

Am I missing something?

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 12:37       ` Henry S. Thompson
@ 2013-03-04 13:17         ` Corinna Vinschen
  2013-03-04 13:21           ` Henry S. Thompson
                             ` (2 more replies)
  0 siblings, 3 replies; 17+ messages in thread
From: Corinna Vinschen @ 2013-03-04 13:17 UTC (permalink / raw)
  To: cygwin

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=003D0000
> >>eax=003D0000 ebx=00000000 ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78
> >>ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe, pid 11572, thread main
> >>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> >>Stack trace:
> >>Frame     Function  Args
> >>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
> >>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
> >>End of stack trace
> >>
> >>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000
> >>eax=003D0000 ebx=00000000 ecx=7792389A edx=0112017C esi=61006C50 edi=0028CD78
> >>ebp=0028AC88 esp=0028AC4C program=C:\cygwin\usr\local\bin\xemacs-21.5-b33.exe, pid 10904, thread main
> >>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> >>Stack trace:
> >>Frame     Function  Args
> >>0028AC88  003D0000  (61273B28, 00000000, 00000000, 00000000)
> >>0028ACF8  61006CF5  (00000000, 0028CD78, 61006C50, 00000000)
> >>End of stack trace
> >>
> >
> > This address indicates that the error is in user code, so this again
> > devolves to something that Marco would likely have to look into.  The
> > "003D0000" looks like a DLL which has not been properly rebased.
> >
> > If you can duplicate this under gdb then "info shared" should tell you
> > which dll is associated with that address.
> 
> Sorry if I've not understood correctly, but when I catch the segfault
> in gdb, info shared doesn't show anything loaded in that address
> range:
> 
> (gdb) info shared

Since you're running GDB anyway, what does `bt' print when the SEGV
occured?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 13:17         ` Corinna Vinschen
@ 2013-03-04 13:21           ` Henry S. Thompson
  2013-03-04 14:25             ` Corinna Vinschen
  2013-03-04 14:20           ` marco atzeri
  2013-03-04 16:20           ` Christopher Faylor
  2 siblings, 1 reply; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-04 13:21 UTC (permalink / raw)
  To: cygwin

Corinna Vinschen writes:

> Since you're running GDB anyway, what does `bt' print when the SEGV
> occured?

   #0  0x003d0000 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 ()
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/dcrt0.cc:861
   #3  0x6100537d in _cygtls::call2 (this=<optimized out>,
       func=0x61006c50 <dll_crt0_1(void*)>, arg=0x0,
       buf=0x6100551b <_cygtls::call(unsigned long (*)(void*, void*),
   void*)+91>)
       at
   /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/cygtls.cc:99
   #4  0x0028ff48 in ?? ()
   #5  0x00641572 in cygwin_crt0 (f=0x458b7f <main>)
       at
   /usr/src/debug/cygwin-1.7.17-1/winsup/cygwin/lib/cygwin_crt0.c:22
   #6  0x00401015 in mainCRTStartup ()
       at /usr/src/debug/cygwin-1.7.17-1/winsup/cygwin/crt0.c:29

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-03 16:18     ` marco atzeri
@ 2013-03-04 13:21       ` Henry S. Thompson
  2013-03-04 14:16         ` marco atzeri
  0 siblings, 1 reply; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-04 13:21 UTC (permalink / raw)
  To: cygwin

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 +0000, 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 compiled xemacs.
>
> I am aware of the issue on postgresql, and working on a real solution,
> plus a workaround for short term.
>
> It is due to bad dll's built by "dlltool+dllwrap" that crash
> after rebase and the only real solution seems to switch
> on "gcc -shared"

Not clear why this is showing up for xemacs then -- it builds no
dlls, just an exe.  What dlls are you seeing a problem with?

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 13:21       ` Henry S. Thompson
@ 2013-03-04 14:16         ` marco atzeri
  2013-03-04 14:19           ` Henry S. Thompson
  0 siblings, 1 reply; 17+ messages in thread
From: marco atzeri @ 2013-03-04 14:16 UTC (permalink / raw)
  To: cygwin

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 +0000, 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 compiled xemacs.
>>
>> I am aware of the issue on postgresql, and working on a real solution,
>> plus a workaround for short term.
>>
>> It is due to bad dll's built by "dlltool+dllwrap" that crash
>> after rebase and the only real solution seems to switch
>> on "gcc -shared"
>
> Not clear why this is showing up for xemacs then -- it builds no
> dlls, just an exe.  What dlls are you seeing a problem with?
>
> ht
>

I am only referring to postgresql, I know nothing about xemacs

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 14:16         ` marco atzeri
@ 2013-03-04 14:19           ` Henry S. Thompson
  0 siblings, 0 replies; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-04 14:19 UTC (permalink / raw)
  To: cygwin

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 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 13:17         ` Corinna Vinschen
  2013-03-04 13:21           ` Henry S. Thompson
@ 2013-03-04 14:20           ` marco atzeri
  2013-03-04 16:20           ` Christopher Faylor
  2 siblings, 0 replies; 17+ messages in thread
From: marco atzeri @ 2013-03-04 14:20 UTC (permalink / raw)
  To: cygwin

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 pure luck for 1.7.17


> Corinna

Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 13:21           ` Henry S. Thompson
@ 2013-03-04 14:25             ` Corinna Vinschen
  0 siblings, 0 replies; 17+ messages in thread
From: Corinna Vinschen @ 2013-03-04 14:25 UTC (permalink / raw)
  To: cygwin

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  0x003d0000 in ?? ()
>    #1  0x610fcf7c in pthread::init_mainthread ()
>        at
>    /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/thread.cc:336

This piece of code hasn't changed since 2011.  The jump to 0x003d0000
looks pretty bad, and it's very lielly not a problem in the Cygwin DLL,
given that this code is called for every single non-forked process.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 13:17         ` Corinna Vinschen
  2013-03-04 13:21           ` Henry S. Thompson
  2013-03-04 14:20           ` marco atzeri
@ 2013-03-04 16:20           ` Christopher Faylor
  2013-03-06 23:05             ` marco atzeri
  2 siblings, 1 reply; 17+ messages in thread
From: Christopher Faylor @ 2013-03-04 16:20 UTC (permalink / raw)
  To: cygwin

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 exposes more of the
stack.

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.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-04 16:20           ` Christopher Faylor
@ 2013-03-06 23:05             ` marco atzeri
  2013-03-07 10:42               ` Henry S. Thompson
  0 siblings, 1 reply; 17+ messages in thread
From: marco atzeri @ 2013-03-06 23:05 UTC (permalink / raw)
  To: cygwin

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's why I asked for the stackdump file since it exposes more of the
> stack.
>
> 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.
>
> cgf
>

just uploaded a test version 9.2.3-1

- Every dll  is built with  "gcc -shared",
- DLLWRAP is not used anymore
- DLLTOLL is only used for postgres.exe

it works on my 20130301 after rebase

Regards
Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: segfault in recent snapshots
  2013-03-06 23:05             ` marco atzeri
@ 2013-03-07 10:42               ` Henry S. Thompson
  0 siblings, 0 replies; 17+ messages in thread
From: Henry S. Thompson @ 2013-03-07 10:42 UTC (permalink / raw)
  To: cygwin

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
>
> - Every dll  is built with  "gcc -shared",
> - DLLWRAP is not used anymore
> - DLLTOLL is only used for postgres.exe
>
> it works on my 20130301 after rebase

And it works (for psql) on my 20130301, and it fixes my earlier
parallel problem with new-build xemacs.  Thanks!

Gold star?

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2013-03-07 10:42 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-02 20:00 segfault in recent snapshots Henry S. Thompson
2013-03-02 20:25 ` Henry S. Thompson
2013-03-02 20:29 ` Christopher Faylor
2013-03-03 12:02   ` Henry S. Thompson
2013-03-03 16:18     ` marco atzeri
2013-03-04 13:21       ` Henry S. Thompson
2013-03-04 14:16         ` marco atzeri
2013-03-04 14:19           ` Henry S. Thompson
2013-03-03 18:06     ` Christopher Faylor
2013-03-04 12:37       ` Henry S. Thompson
2013-03-04 13:17         ` Corinna Vinschen
2013-03-04 13:21           ` Henry S. Thompson
2013-03-04 14:25             ` Corinna Vinschen
2013-03-04 14:20           ` marco atzeri
2013-03-04 16:20           ` Christopher Faylor
2013-03-06 23:05             ` marco atzeri
2013-03-07 10:42               ` Henry S. Thompson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).