| standard vs managed make project and gdb differences [message #179479] |
Thu, 09 November 2006 12:37  |
Eclipse User |
|
|
|
Originally posted by: shawn.protsman.patownsend.com
This may be a configuration issue on my part. I've created a Managed Make
C with the following test app:
1 #include <stdio.h>
2 int main(int argc, char **argv)
3 {
4 int idx = 0;
5 for (idx = 0; idx < 10; ++idx)
6 (void)printf("foo <%2d>\n", idx);
7 return 0;
8 }
I run it through debug within CDT and everything works just fine. If I
create a new Standard Make C project with the same code as above and run
it through the debugger (verbose mode) it doesn't work correctly. It will
pass right by any breakpoint. The CDT console reports:
153-break-insert foo.c:6
&"No source file named foo.c.\n"
153^done
(gdb)
154-break-insert -t main
154^done,bkpt={number="1",type="breakpoint",disp="del",enabled= "y",addr="0x080483b4",at="<main>",times="0"}
(gdb)
<snip>
~"Program stopped at 0xb7f12ff0.\n"
~"It stopped at a breakpoint that has since been deleted.\n"
You see, it reports that it cannot find the file named foo.c which is
rather odd. This explains why it just seems to ignore the breakpoint. This
works fine with Managed but not with Standard so that led me to believe
I've got a configuration setting/issue that I'm unaware of when using
Standard Make projects. Any help will be greatly appreciated!
Platform information:
SUSE Linux Enterprise Desktop 10 (i586)
Java version "1.5.0_06"
Eclipse 3.2.1
CDT 3.1.1
gdb-6.4-19.10
gcc (GCC) 4.1.0 (SUSE Linux)
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04762 seconds
Home