X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,TW_CG,TW_VP,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20100419174819.GA6110@ednor.casa.cgf.cx>
References: <m2r9d1cfe481004181509tb0853403qf8129030c0059f00 AT mail DOT gmail DOT com> 	 <4BCBAFF0 DOT 9080701 AT gmail DOT com> 	 <20100419063229 DOT GA26209 AT ednor DOT casa DOT cgf DOT cx> 	 <u2v9d1cfe481004190444la24cacabs4ac2ee530018b030 AT mail DOT gmail DOT com> 	 <4BCC6D32 DOT 4060708 AT cygwin DOT com> 	 <20100419174819 DOT GA6110 AT ednor DOT casa DOT cgf DOT cx>
Date: Tue, 20 Apr 2010 09:19:28 +0300
Received: by 10.204.152.2 with SMTP id e2mr236212bkw.81.1271744368875; Mon, 19  	Apr 2010 23:19:28 -0700 (PDT)
Message-ID: <v2x9d1cfe481004192319s5e32c785hf4f8b42d56712c57@mail.gmail.com>
Subject: Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
From: Yuval Emek <yuval DOT emek AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
>>> <cgf-use-the-mailinglist-please...> =A0wrote:
>> =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. =A0Feeding spammers just mak=
es
>>them hungry.
>>
>><snip>
>>
>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>>>> in cygwin_attach_dll. =A0It is supposed to be set to the address of the
>>>> "environ" variable in the DLL. =A0It is not supposed to be NULL. =A0Th=
at
>>>> assignment should actually not even be necessary but the fact that
>>>> envptr may be NULL is a problem. =A0Of course, it could just be some
>>>> non-NULL garbage too. =A0Running in gdb and getting a stack trace woul=
d be
>>>> instructive.
>>>
>>> Can you be more specific? (I have been using cygwin for a while, but I
>>> never debugged it beforehand.)
>>> I can install gdb using setup.exe . What should I do then in order to
>>> obtain a stack trace?
>>
>>Grab a snapshot from <http://cygwin.com/snapshots/>. =A0You want the DLL
>>and debugging info at least.
>
> And, assuming that you can actually run gdb, just "gdb bash" and then "r".

I installed gdb and then downloaded the (latest) snapshots of
cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the
previous cygwin1.dll) .
Running gdb bash seems to fail since there are no debugging symbols.
In particular, when typing r in the gdb prompt, I get the following
output:

Starting program: /usr/bin/bash
[New thread 3800.0x15b4]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New thread 3800.0x13f4]

[1]+  Stopped                 gdb bash

(Makes sense, I guess, as bash was not compiled with debugging info.)
Can I download debugging info for bash from somewhere? (As far as I
understand, I don't even have the source code for bash.)
Is there something else I can do?

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

--
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