From: Jim Blandy <jimb@redhat.com>
To: "Kiran Chandrashekaran, Nair (IE10)" <Kiran.Nair@honeywell.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB Remote Debugging Problem
Date: Fri, 31 Oct 2003 22:27:00 -0000 [thread overview]
Message-ID: <vt2r80tyrdt.fsf@zenia.home> (raw)
In-Reply-To: <77ED2BF75D59D1439F90412CC5B109740373EAEF@ie10-sahara.hiso.honeywell.com>
That certainly doesn't sound like normal behavior.
But unless we can reproduce the problem ourselves, we can't do much
about it. I suspect there's some problem with your stub. When you
say "set debug remote 1", does it seem to be doing all the right things?
"Kiran Chandrashekaran, Nair (IE10)" <Kiran.Nair@honeywell.com> writes:
> Hi all,
>
> I have a gdb stub,running on my target.
> I am able to connect to the target through TCP and debug
> my debug from the host.
>
> My Problem is
> 1. I get a SIGTRAP received message for every function call,
> even if I am not stepping into the function or have not set a breakpoint
> in
> the function.
> I get the SRC_AND_LOC message always,when ideally I should only the
> the SRC_LINE displayed.
> eg: When I step through a function foo() in function xyz() I get
>
> xyx () at xyz.c:78
>
> 2. Also when a breakpoint is hit ,The don't get the Breakpoint number
> displayed.
> I get the SRC_AND_LOC displayed,but no breakpoint info.
>
> What could be the problem.
> I am using gdb 6.0 configured for i386-elf on cygwin
>
> Could anything be possibily wrong with my gdb stub,which is
> derived from the basic gdb stub.
>
> Thanks
> Kiran
next prev parent reply other threads:[~2003-10-31 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 8:03 Kiran Chandrashekaran, Nair (IE10)
2003-10-31 22:27 ` Jim Blandy [this message]
2003-11-03 6:24 ` regarding tracepoint support on a stub ankit thukral
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=vt2r80tyrdt.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=Kiran.Nair@honeywell.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).