This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
RE: Developing for Insight
- From: "Liang, James" <jliang at sandia dot gov>
- To: "'Keith Seitz'" <keiths at redhat dot com>
- Cc: "'insight at sources dot redhat dot com'" <insight at sources dot redhat dot com>
- Date: Tue, 22 Apr 2003 14:52:28 -0600
- Subject: RE: Developing for Insight
Something else I forgot to mention that may clear things up.
Recall I said the source window is stack on main.c at function main. Well,
if I hit the
stack button, it will show me my call stack. If I click on one of the
functions in the call stack, it has no trouble updating the code window to
match. Funny. disassembly still doesn't work though
-----Original Message-----
From: Keith Seitz [mailto:keiths at redhat dot com]
Sent: Tuesday, April 22, 2003 12:46 PM
To: Liang, James
Cc: 'insight at sources dot redhat dot com'
Subject: RE: Developing for Insight
On Tue, 2003-04-22 at 11:18, Liang, James wrote:
> (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 {}
Ok, so what we see is that both Insight and GDB think you're at the same
place, in func2() at /home/jliang/testProg/test.c:79. So the SrcWin or
SrcTextWin is screwing up. Are you sure that the debug window reported
no errors? Perhaps it would be best to send your insight.log for the
session?
[Reming me again: what codebase are you working with? Host platform?]
Keith