public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Benjamin P Myers <dative@sukrahelitek.com>
To: gdb@sources.redhat.com
Subject: Re: init.c:  No such file or directory.
Date: Mon, 09 Jun 2003 20:09:00 -0000	[thread overview]
Message-ID: <200306091508.59192.dative@sukrahelitek.com> (raw)
In-Reply-To: <20030609194144.GA10114@nevyn.them.org>

On Monday 09 June 2003 14:41, Daniel Jacobowitz wrote:
> Is it a problem?  Can you list your program's entry point and set
> breakpoints?
>
> That suggests that the init.c is coming from gcc/glibc, and has debug
> information.  It's not associated with your application.

It is a problem more for the other people I work with than I, because they 
debug quite a bit more fortran code (and like to use ddd, which this seems to 
break).

I think this is what you mean, right?

> gcc -gdwarf hello.c
> ~/bin/gdb ./a.out
GNU gdb 5.3
<snip>
(gdb) list hello.c:main
No source file named hello.c.
(gdb) break hello.c:6
No source file named hello.c.
(gdb)

vs.

> gcc -g hello.c
> ~/bin/gdb ./a.out
<snip>
(gdb) list hello.c:main
1       #include <stdio.h>
2
3       int
4       main ()
5       {
6         printf("Hello, World\n");
7       }
(gdb) break hello.c:6
Breakpoint 1 at 0x804834c: file hello.c, line 6.
(gdb)

Not much luck.  /lib/libc.so.6 is not stripped.  Are you suggesting I do so?

Thanks for your help.
-Ben



  reply	other threads:[~2003-06-09 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 19:34 Benjamin P Myers
2003-06-09 19:42 ` Daniel Jacobowitz
2003-06-09 20:09   ` Benjamin P Myers [this message]
2003-06-09 20:17     ` Daniel Jacobowitz
2003-06-09 20:41       ` Benjamin P Myers

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=200306091508.59192.dative@sukrahelitek.com \
    --to=dative@sukrahelitek.com \
    --cc=gdb@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).