From: "Dave Arnold" <avr_fan@nettaxi.com>
To: <insight@sourceware.cygnus.com>
Cc: <insight@sourceware.cygnus.com>
Subject: Re: Any Clues about this problem? Close but...
Date: Fri, 07 Jul 2000 22:52:00 -0000 [thread overview]
Message-ID: <009301bfe8a1$e0070b80$65241004@homepc.freedsl.com> (raw)
-----Original Message-----
From: Chris Faylor <cgf@cygnus.com>
To: Dave Arnold <avr_fan@mailandnews.com>
Cc: insight@sourceware.cygnus.com <insight@sourceware.cygnus.com>
Date: Friday, July 07, 2000 10:15 PM
Subject: Re: Any Clues about this problem?
>On Fri, Jul 07, 2000 at 10:17:54PM -0700, Dave Arnold wrote:
>>Anyone have a clue why I can't list the source for the program I'm
debuggin
>>using insight?
>>
>>(gdb) list
>>1 /cygnus/netrel/src/cygwin-1.1.2/winsup/cygwin/libccrt0.cc: No
such
>>file or directory.
>>
>>This path is strange, I don't think it exists anywhere under my cygwin
root.
>
>The path is coming from the cygwin DLL. You don't want that. That is the
location
>of the 'libccrt0.cc' file on my machine from when I make a cygwin net
release.
>
>Try 'list main'.
>
>Are you *sure* you're both compiling and linking with the '-g' option?
When
>I type just 'list' I get my 'main'.
That is a good question because after taking a close look I discovered a big
mistake on my part. I commented out the -g variable definition in the top of
the makefile.
CC = gcc
# CFLAGS = -g
load: load5.o btlib.o
$(CC) $(CFLAGS) load5.o btlib.o -o load
However I recompiled with -g for sure and still
I got this output:
(gdb) list
1 frame.c: No such file or directory.
(gdb) list main
Error: No line number known for main.
(gdb)
>cgf
next reply other threads:[~2000-07-07 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 22:52 Dave Arnold [this message]
2000-07-08 14:28 ` Chris Faylor
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='009301bfe8a1$e0070b80$65241004@homepc.freedsl.com' \
--to=avr_fan@nettaxi.com \
--cc=insight@sourceware.cygnus.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).