From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: How to break cygwin inside dcrt0.cc ?
Date: Fri, 05 May 2017 10:06:00 -0000 [thread overview]
Message-ID: <48d5fc33-9034-19bd-fc94-10977535ec3c@dronecode.org.uk> (raw)
In-Reply-To: <14756c6c-cc89-fa5d-bfbb-88662445dc46@gmail.com>
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
>>>
>>> break child_info_fork::alloc_stack
>>> Function "child_info_fork::alloc_stack" not defined.
>>>
>>> break /usr/src/debug/cygwin-2.8.0-1/winsup/cygwin/dcrt0.cc:408
>>> No source file named
>>> /usr/src/debug/cygwin-2.8.0-1/winsup/cygwin/dcrt0.cc
This works for me:
> $ gdb test.exe
[...]
> Reading symbols from test.exe...done.
> (gdb) b main
> Breakpoint 1 at 0x1004010dd: file test.c, line 7.
> (gdb) r
> Starting program: /wip/test.exe
>
> Thread 1 "test" hit Breakpoint 1, main () at while-test.c:7
> 7 sleep(1);
> (gdb) b child_info_fork::alloc_stack()
> Breakpoint 2 at 0x1800463f0: file /usr/src/debug/cygwin-2.8.0-1/winsup/cygwin/dcrt0.cc, line 407.
> (gdb)
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...
> 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.
> $ 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...
--
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
next prev parent reply other threads:[~2017-05-05 10:06 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 [this message]
2017-05-05 13:25 ` Marco Atzeri
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=48d5fc33-9034-19bd-fc94-10977535ec3c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).