From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How to break cygwin inside dcrt0.cc ?
Date: Fri, 05 May 2017 13:25:00 -0000 [thread overview]
Message-ID: <e7ac1103-178f-20bf-9fa0-04735c7f38e3@gmail.com> (raw)
In-Reply-To: <48d5fc33-9034-19bd-fc94-10977535ec3c@dronecode.org.uk>
On 05/05/2017 12:05, Jon Turney wrote:
> On 05/05/2017 08:44, Marco Atzeri wrote:
>> On 05/05/2017 04:01, Mark Geisert wrote:
>>> Marco Atzeri wrote:
>>>> I am likely missing something obvious, but I do not succeed to put
>>>> a breakpoint inside child_info_fork::alloc_stack
>>>>
>
> You are in a state where the debug info for cygwin1.dll has been loaded?
> Trying to set a breakpoint before the program has run won't work, as
> cygwin1.dll hasn't loaded yet...
there is something else.
But I don't understand if it is the specific program,
the 32bit system on WOW or just a crazy BLODA in new
behaviors...
>
>> By the way it seems that git source can not be built
>> in cygwin as it lacks configure
>
> What? The configure script is in the git repo and source tarball.
it seems my git repo copy was damaged.
Cloned again from scratch and configure appeared again :-((
>
>> $ autoreconf
>> configure.ac:33: error: Please use exactly Autoconf 2.64 instead of 2.69.
>> config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
>> configure.ac:33: the top level
>> autom4te-2.69: /usr/bin/m4 failed with exit status: 1
>> aclocal-1.14: error: echo failed with exit status: 1
>> autoreconf-2.69: aclocal failed with exit status: 1
>
> This version of autoconf is packaged as gcc-tools-epoch2-autoconf. The
> announce mail for that explains how to use it.
>
> Moving off such ancient autotools needs to be done, but SHTDI...
as usual..
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
prev parent reply other threads:[~2017-05-05 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:08 Marco Atzeri
2017-05-05 1:17 ` Mark Geisert
2017-05-05 2:01 ` Mark Geisert
2017-05-05 7:44 ` Marco Atzeri
2017-05-05 8:47 ` Mark Geisert
2017-05-05 10:06 ` Jon Turney
2017-05-05 13:25 ` Marco Atzeri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7ac1103-178f-20bf-9fa0-04735c7f38e3@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).