From: Peter Barada <peter@the-baradas.com>
To: gdb@sources.redhat.com
Subject: Re: message: "Cannot find bounds of current function"
Date: Fri, 25 Mar 2005 17:31:00 -0000 [thread overview]
Message-ID: <20050325173111.EA8E398473@baradas.org> (raw)
In-Reply-To: <BAY13-F41B6C4FB3F3107B427AF6DD8410@phx.gbl> (jjosburn@hotmail.com)
>what does that message mean?
>i have start a executeable remotely via the command:
>gdbserver 192.168.0.10:1234 ./stubs
>
>
>(gdb) file /tmp/stubs/src/stubs
>Reading symbols from /tmp/stubs/src/stubs...done.
>(gdb) target extended-remote 192.168.0.10:1234
>Remote debugging using 192.168.0.10:1234
>0x400009c0 in ?? ()
>(gdb) break main
>Breakpoint 1 at 0x8048338: file main.c, line 8.
>(gdb) n
>Cannot find I bounds of current function
>(gdb)
You *really* should read the documentation a bit deeper.
This is because when you attached to gdbserver, the process under
debug has not completed the C start-up code.
If you had 'objdump -h' the program you are trying to debug, you
would have found that 0x400009c0 is is *way* outside the bounds of the
program.
If instead you tried:
(gdb) target extended-remote 192.168.0.10:1234
Remote debugging using 192.168.0.10:1234
0x400009c0 in ?? ()
(gdb) break main
Breakpoint 1 at 0x8048338: file main.c, line 8.
(gdb) c
Breakpoint 1, main ( ... )
at /.../main.c:8
(gdb)
At this point the program counters is *inside* your program and gdb
can match up the program counter to source code.
--
Peter Barada
peter@the-baradas.com
prev parent reply other threads:[~2005-03-25 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 17:01 james osburn
2005-03-25 17:31 ` Peter Barada [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=20050325173111.EA8E398473@baradas.org \
--to=peter@the-baradas.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