From: Kristian Otnes <kristian.otnes@tevero.no>
To: insight <insight@sources.redhat.com>
Subject: RE: Problem with source paths with new Cygwin release
Date: Thu, 04 Sep 2003 21:12:00 -0000 [thread overview]
Message-ID: <3F579D1C@webmail.aktivepost.no> (raw)
>Try:
>
>$ gdb myexecutable
>(gdb) list FUNCTION
>
This would typically give a GDB printout:
879 foo.c: No such file or directory.
in foo.c
whereas it shows a few lines of C code if I use the older
cygwin/cygutils modules
>Try setting breakpoints and running, too:
>
>(gdb) break FUNCTION
>(gdb) run
Setting a break point at a valid function works. When the
CPU gets there, it is halted, and Insight will only show the
assembly code.
Kristian Otnes (kristian.otnes@tevero.no)
Tevero AS (www.tevero.no)
P.O.Box 96
NO-1317 Baerums Verk
Norway
Phone: +47 67 56 29 95
next reply other threads:[~2003-09-04 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 21:12 Kristian Otnes [this message]
2003-09-04 21:29 ` Keith Seitz
2003-09-04 21:56 ` Kristian Otnes
2003-09-04 22:02 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 20:45 Kristian Otnes
2003-09-05 9:38 Kristian Otnes
2003-09-04 20:47 Kristian Otnes
2003-09-04 20:52 ` Keith Seitz
2003-09-04 19:57 Kristian Otnes
2003-09-04 20:11 ` Keith Seitz
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=3F579D1C@webmail.aktivepost.no \
--to=kristian.otnes@tevero.no \
--cc=insight@sources.redhat.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).