From: Andrey Khalyavin <halyavin@google.com>
To: cygwin@cygwin.com
Subject: Re: GDB behaves differently on the final cygwin1.dll 1.7.16 and on a previous one.
Date: Fri, 24 Aug 2012 12:47:00 -0000 [thread overview]
Message-ID: <CACgPhYro_sDrwyoK_-_VepROj-Q+Fzpgq4Sy0RP7NJjf1f-oAQ@mail.gmail.com> (raw)
On Fri, 24 Aug 2012 01:45:11 +0400, Evgeny Tarasov wrote:
>Well,
>
>I've got two different cygwin1.dll's of 1.7.16 version.
>The first one was obtained from cvs and built by myself (is it attached to 5th june, 2012; as uname -a says)
>The other one is of final 20 july, 2012 ver.
>
>So my question is the following:
>Why the same GDB does not want to put breakpoints to the same (and any) source when I work with the latest of the two.
>I always have completely updated cygwin installation, but in order to debug, i have to replace the latest cygwin1.dll with the previous.
You need to install Debug/cygwin-debuginfo package. Then you will be
able to set breakpoints by line:
(gdb) symbol-file cygwin1.dll
Reading symbols from /usr/bin/cygwin1.dll...Reading symbols from
/usr/lib/debug/usr/bin/cygwin1.dbg...done.
done.
(gdb) b _cygtls::call2
Breakpoint 1 at 0x610050e0: file
/usr/src/debug/cygwin-1.7.16-1/winsup/cygwin/cygtls.cc, line 92.
Andrey Khalyavin
--
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 reply other threads:[~2012-08-24 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:47 Andrey Khalyavin [this message]
[not found] ` <836101345823425@web22d.yandex.ru>
2012-08-25 6:12 ` Andrey Khalyavin
-- strict thread matches above, loose matches on Subject: below --
2012-08-25 5:41 Evgeny Tarasov
2012-08-24 11:45 Evgeny Tarasov
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=CACgPhYro_sDrwyoK_-_VepROj-Q+Fzpgq4Sy0RP7NJjf1f-oAQ@mail.gmail.com \
--to=halyavin@google.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).