CDT Debug issue

Discussion:

CDT Debug issue

Avinash Sawant

2008-12-01 07:30:05 UTC

Hi ,

I installed setup for ARM hardware using YAGARTO and Eclipse.

I have interface between eclips and ARM as
PC Eclips -> CDT debug -> BDI 3000 -> ARM Board

when I debug it I got the error as
*No symbol "new" in current context.*

Has anyone of you came across this error earlier.

For your reference attached the log of console window here. I am not
gettting where I am going wrong can you help me to solve the issue with the
ARM hardware debug.

Thanks a lot .. !!
Avinash

--------------------------------------------------------------------------------------

83-gdb-set confirm off

83^done

(gdb)

84-gdb-set width 0

84^done

(gdb)

85-gdb-set height 0

85^done

(gdb)

86-interpreter-exec console echo

86^done

(gdb)

87-gdb-show prompt

87^done,value="(gdb) "

(gdb)

88-gdb-set new-console on

No symbol "new" in current context.

&"No symbol \"new\" in current context.\n"

88^error,msg="No symbol \"new\" in current context."

(gdb)

89 target remote 192.168.0.24:23

target remote 192.168.0.24:23

&"target remote 192.168.0.24:23\n"

&"192.168.0.24:23: A connection attempt failed because the connected party
did not properly respond after a period of time, or established connection
failed because connected host has failed to respond.\n"

192.168.0.24:23: A connection attempt failed because the connected party did
not properly respond after a period of time, or established connection
failed because connected host has failed to respond.

89^error,msg="192.168.0.24:23: A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to respond."

(gdb)

90 monitor reset run

&"monitor reset run\n"

monitor reset run

&"\"monitor\" command not supported by this target.\n"

"monitor" command not supported by this target.

90^error,msg="\"monitor\" command not supported by this target."

(gdb)

91 monitor delay 3000

&"monitor delay 3000\n"

&"\"monitor\" command not supported by this target.\n"

monitor delay 3000

"monitor" command not supported by this target.

91^error,msg="\"monitor\" command not supported by this target."

(gdb)

92 monitor halt

&"monitor halt\n"

&"\"monitor\" command not supported by this target.\n"

92^error,msg="\"monitor\" command not supported by this target."

(gdb)

93

monitor halt

"monitor" command not supported by this target.

&"\n"

93^done

(gdb)

94-environment-directory D:/yagarto_ARM_BDI/workspace/STR7Test
D:/yagarto_ARM_BDI/workspace/STR7Test/.dep
D:/yagarto_ARM_BDI/workspace/STR7Test/.settings
D:/yagarto_ARM_BDI/workspace/STR7Test/inc
D:/yagarto_ARM_BDI/workspace/STR7Test/prj
D:/yagarto_ARM_BDI/workspace/STR7Test/src

94^done,source-path="D:/yagarto_ARM_BDI/workspace/STR7Test;D:/yagarto_ARM_BDI/workspace/STR7Test/.dep;D:/yagarto_ARM_BDI/workspace/STR7Test/.settings;D:/yagarto_ARM_BDI/workspace/STR7Test/inc;D:/yagarto_ARM_BDI/workspace/STR7Test/prj;D:/yagarto_ARM_BDI/workspace/STR7Test/src;$cdir;$cwd"

(gdb)

95 info threads

&"info threads\n"

&"No registers.\n"

95^error,msg="No registers."

(gdb)

96-data-list-register-names

96^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","sp","lr","pc","f0","f1","f2","f3","f4","f5","f6","f7","fps","cpsr","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","",""]

(gdb)

97

&"\n"

97^done

(gdb)

--------------------------------------------------------------------------------

Subs

2008-12-01 07:38:24 UTC

Permalink

This is not a group for users. You should post to the eclipse.tools.cdt
newsgroup.

However, *No symbol "new" in current context.* is not an error. It is
caused by Eclipse trying to provide context information on the symbol
under the mouse cursor. It does this in a dumb fashion by just trying to
perform a (gdb) lookup on any word that is under the cursor (it could be
a comment, a symbol, anything). If a valid response is received, it
displays it. You are seeing gdb report that it is not a vlid symbol.

Post by Avinash Sawant
Hi ,
I installed setup for ARM hardware using YAGARTO and Eclipse.
I have interface between eclips and ARM as
PC Eclips -> CDT debug -> BDI 3000 -> ARM Board
when I debug it I got the error as
*No symbol "new" in current context.*
Has anyone of you came across this error earlier.
For your reference attached the log of console window here. I am not
gettting where I am going wrong can you help me to solve the issue with
the ARM hardware debug.
Thanks a lot .. !!
Avinash
--------------------------------------------------------------------------------------
83-gdb-set confirm off
83^done
(gdb)
84-gdb-set width 0
84^done
(gdb)
85-gdb-set height 0
85^done
(gdb)
86-interpreter-exec console echo
86^done
(gdb)
87-gdb-show prompt
87^done,value="(gdb) "
(gdb)
88-gdb-set new-console on
No symbol "new" in current context.
&"No symbol \"new\" in current context.\n"
88^error,msg="No symbol \"new\" in current context."
(gdb)
89 target remote 192.168.0.24:23 <http://192.168.0.24:23>
target remote 192.168.0.24:23 <http://192.168.0.24:23>
&"target remote 192.168.0.24:23\n"
&"192.168.0.24:23 <http://192.168.0.24:23>: A connection attempt failed
because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed
to respond.\n"
192.168.0.24:23 <http://192.168.0.24:23>: A connection attempt failed
because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed
to respond.
89^error,msg="192.168.0.24:23 <http://192.168.0.24:23>: A connection
attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because
connected host has failed to respond."
(gdb)
90 monitor reset run
&"monitor reset run\n"
monitor reset run
&"\"monitor\" command not supported by this target.\n"
"monitor" command not supported by this target.
90^error,msg="\"monitor\" command not supported by this target."
(gdb)
91 monitor delay 3000
&"monitor delay 3000\n"
&"\"monitor\" command not supported by this target.\n"
monitor delay 3000
"monitor" command not supported by this target.
91^error,msg="\"monitor\" command not supported by this target."
(gdb)
92 monitor halt
&"monitor halt\n"
&"\"monitor\" command not supported by this target.\n"
92^error,msg="\"monitor\" command not supported by this target."
(gdb)
93
monitor halt
"monitor" command not supported by this target.
&"\n"
93^done
(gdb)
94-environment-directory D:/yagarto_ARM_BDI/workspace/STR7Test
D:/yagarto_ARM_BDI/workspace/STR7Test/.dep
D:/yagarto_ARM_BDI/workspace/STR7Test/.settings
D:/yagarto_ARM_BDI/workspace/STR7Test/inc
D:/yagarto_ARM_BDI/workspace/STR7Test/prj
D:/yagarto_ARM_BDI/workspace/STR7Test/src
94^done,source-path="D:/yagarto_ARM_BDI/workspace/STR7Test;D:/yagarto_ARM_BDI/workspace/STR7Test/.dep;D:/yagarto_ARM_BDI/workspace/STR7Test/.settings;D:/yagarto_ARM_BDI/workspace/STR7Test/inc;D:/yagarto_ARM_BDI/workspace/STR7Test/prj;D:/yagarto_ARM_BDI/workspace/STR7Test/src;$cdir;$cwd"
(gdb)
95 info threads
&"info threads\n"
&"No registers.\n"
95^error,msg="No registers."
(gdb)
96-data-list-register-names
96^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","sp","lr","pc","f0","f1","f2","f3","f4","f5","f6","f7","fps","cpsr","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","",""]
(gdb)
97
&"\n"
97^done
(gdb)
--------------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________
cdt-debug-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev

--
Subs

Elena Laskavaia

2008-12-01 15:01:01 UTC

Permalink

this gdb you have does not understand some commands like set new-console on
and monitor - which is used in this integration. Most of the jtag stuff would not work in this case.

Daniel Jacobowitz

2008-12-01 15:12:09 UTC

Permalink

Post by Elena Laskavaia
this gdb you have does not understand some commands like set new-console on
and monitor - which is used in this integration. Most of the jtag stuff would not work in this case.

The new-console failure is probably harmless. The reason monitor

Post by Elena Laskavaia

Post by Avinash Sawant
(gdb)
89 target remote 192.168.0.24:23 <http://192.168.0.24:23>
target remote 192.168.0.24:23 <http://192.168.0.24:23>
&"target remote 192.168.0.24:23\n"
&"192.168.0.24:23 <http://192.168.0.24:23>: A connection attempt failed
because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed
to respond.\n"

So, fix that...

--
Daniel Jacobowitz
CodeSourcery

Continue reading on narkive:

Search results for 'CDT Debug issue' (Questions and Answers)

replies

What is a good C++ compiler?

started 2012-12-30 16:08:56 UTC

programming & design

replies

eclipse c++, can't get compiler working >.

started 2009-07-21 13:13:03 UTC

programming & design