From: "Liang, James" <jliang@sandia.gov>
To: "'Keith Seitz'" <keiths@redhat.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: RE: Developing for Insight
Date: Tue, 22 Apr 2003 18:18:00 -0000 [thread overview]
Message-ID: <71251C7D5FB1D2119C8F0008C7A44ED103792010@es07snlnt.sandia.gov> (raw)
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Ok...
-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com]
Sent: Tuesday, April 22, 2003 11:54 AM
To: Liang, James
Cc: 'insight@sources.redhat.com'
Subject: RE: Developing for Insight
On Tue, 2003-04-22 at 09:53, Liang, James wrote:
> Actually, more than just the up and down buttons don't work. That was
just
> an example.
> I mean, I can't get Insight to track where I am in the code even though
the
> list command in the console works.
Open a console window and get your target at a breakpoint somewhere
(like main). The procedure will look something like:
(gdb) file FOO
(gdb) set remotebaud XXXX [if necessary]
(gdb) target BLAH [if necessary]
(gdb) load [if necessary]
(gdb) break SOMEWHERE
(gdb) [run or continue]
Now type:
(gdb) f
(gdb) list
(gdb) tk gdb_loc
Send the results of these last three commands to the list. This is just
too goofy.
Keith
[-- Attachment #2: share.txt --]
[-- Type: text/plain, Size: 362 bytes --]
(gdb) f
#0 func2 () at test.c:79
(gdb) list
74 doPrint("Hello\n");
75 #endif
76 INT8U y;
77
78 if (0==retVal)
79 retVal=pparse(retVal,a,b);
80 else
81 return retVal;
82
83 /* function got
(gdb) tk gdb_loc
test.c func2 /home/jliang/testProg/test.c 79 0x33d45 0x0 {}
next reply other threads:[~2003-04-22 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 18:18 Liang, James [this message]
2003-04-22 18:43 ` Keith Seitz
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792016@es07snlnt.sandia.gov>
2003-04-22 23:15 ` Keith Seitz
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792015@es07snlnt.sandia.gov>
2003-04-22 21:45 ` Keith Seitz
2003-04-22 21:47 ` Keith Seitz
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792014@es07snlnt.sandia.gov>
2003-04-22 21:18 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 20:52 Liang, James
2003-04-22 20:39 Liang, James
2003-04-22 20:58 ` Keith Seitz
2003-04-22 18:37 Liang, James
2003-04-22 18:45 ` Keith Seitz
2003-04-22 16:53 Liang, James
2003-04-22 17:52 ` Keith Seitz
2003-04-21 22:23 Liang, James
2003-04-21 22:59 ` Martin M. Hunt
2003-04-10 19:47 Liang, James
2003-04-10 20:05 ` Martin M. Hunt
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=71251C7D5FB1D2119C8F0008C7A44ED103792010@es07snlnt.sandia.gov \
--to=jliang@sandia.gov \
--cc=insight@sources.redhat.com \
--cc=keiths@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).