From: Fernando Nasser <fnasser@redhat.com>
To: Brent Phillips <brent@lyrastudios.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: gdb suddenly unable to read source files?
Date: Sun, 17 Jun 2001 09:03:00 -0000 [thread overview]
Message-ID: <3B2CD3FE.1B436E3@redhat.com> (raw)
In-Reply-To: <5.1.0.14.2.20010616161853.0346cb50@lyrastudios.com>
Which version of gdb?
Which Operation System (version)?
What is the full path to you files?
What is the exact command line you've used to compile your programs?
Compiler version?
You haven't provided us with much info....
Brent Phillips wrote:
>
> Hi,
>
> I've been using gdb successfully for quite some time, and recently a
> strange problem came seemingly out of nowhere. Now, whenever I try to set a
> breakpoint, I always get the error "No line xxx in source file yyy". This
> happens even if I set a breakpoint at line 1 in a file in the same
> directory that gdb is running from. It also happens whether I try to read
> the breakpoints from an init file or type them in manually.
>
> Additionally, when using gdb to inspect a core dump, it no longer is able
> to "list"; it just says
>
> 1 init.c: no such file or directory
>
> But I am able to get a stack trace.
>
> What happened here? How do I fix this? I've tried reinstalling gcc, gdb,
> etc., to no avail...please advise!
>
> Thanks in advance
>
> Brent Phillips
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
prev parent reply other threads:[~2001-06-17 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-16 16:35 Brent Phillips
2001-06-17 9:03 ` Fernando Nasser [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=3B2CD3FE.1B436E3@redhat.com \
--to=fnasser@redhat.com \
--cc=brent@lyrastudios.com \
--cc=gdb@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