Home » Language IDEs » C / C++ IDE (CDT) » uncommon paths gdb Console log file
| uncommon paths gdb Console log file [message #173037] |
Mon, 17 July 2006 08:15  |
Eclipse User |
|
|
|
Hi all,
depend on one of postings in this newsgroup I have changed in the file
C:\Programme\ARM-Eclipse\plugins\org.eclipse.cdt.debug.mi.co re_3.1.0.200606261600
\plugin.xml cpu settings to "*" because I have had error "CPU not
supported" if arm-elf-gdb was used.
The error is away but if I try to start the debugger it kills the debug
session with error:
Execution is suspended because of error.
Don't know how to run. Try "help target".
I have logged the communication to gdb as described in CDT FAQ and used
the verbose CDT console output in CDT. Both outputs are similar as
expected.
The paths in environment-directory and warnings after it seems unusual to
me.
I am using windows and arm-elf-gdb. I can debug this application with the
same GDB as Console but not in Eclipse.
Does anyone about this problem?
Hier the log from GDB Console:
1-gdb-set confirm off
1^done,address="0x40000020",load-size="2446",transfer-rate= "179522",write-rate="815"
(gdb)
2-gdb-set width 0
2^done
(gdb)
3-gdb-set height 0
3^done
(gdb)
4-interpreter-exec console echo
4^done
(gdb)
5-gdb-show prompt
5^done,value="(gdb) "
(gdb)
6-gdb-set new-console
&"No symbol \"new\" in current context.\n"
No symbol "new" in current context.
6^error,msg="No symbol \"new\" in current context."
(gdb)
7-gdb-set new-console
&"No symbol \"new\" in current context.\n"
7^error,msg="No symbol \"new\" in current context."
(gdb)
8-environment-cd C:\\embedded\\workarm\\sample320
No symbol "new" in current context.
8^done
(gdb)
9-environment-directory C /embedded/workarm/sample320;C
/embedded/workarm/sample320/.settings;C
/embedded/workarm/sample320/Cfg-Debug-FLASH;C
/embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C
/embedded/workarm/sample320/Cfg-Debug-FLASH/src;C
/embedded/workarm/sample320/Cfg-Debug-XRAM;C
/embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C
/embedded/workarm/sample320/Cfg-Debug-XRAM/src;C
/embedded/workarm/sample320/inc;C /embedded/workarm/sample320/lib;C
/embedded/workarm/sample320/src;C
&"Warning: /embedded/workarm/sample320/src;C: No such file or directory.\n"
Warning: /embedded/workarm/sample320/src;C: No such file or directory.
&"Warning: /embedded/workarm/sample320/lib;C: No such file or directory.\n"
Warning: /embedded/workarm/sample320/lib;C: No such file or directory.
&"Warning: /embedded/workarm/sample320/inc;C: No such file or directory.\n"
Warning: /embedded/workarm/sample320/inc;C: No such file or directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/src;C: No such file or
directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C: No such file or
directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM;C: No such file or
directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/src;C: No such file
or directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C: No such file
or directory.
Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH;C: No such file or
directory.
Warning: /embedded/workarm/sample320/.settings;C: No such file or
directory.
Warning: /embedded/workarm/sample320;C: No such file or directory.
Warning: /cygdrive/c/embedded/workarm/sample320/C: No such file or
directory.
&"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/src;C: No such file
or directory.\n"
&"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C: No such file
or directory.\n"
&"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM;C: No such file or
directory.\n"
&"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/src;C: No such file
or directory.\n"
&"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C: No such file
or directory.\n"
&"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH;C: No such file or
directory.\n"
&"Warning: /embedded/workarm/sample320/.settings;C: No such file or
directory.\n"
&"Warning: /embedded/workarm/sample320;C: No such file or directory.\n"
&"Warning: /cygdrive/c/embedded/workarm/sample320/C: No such file or
directory.\n"
9^done,source-path=" /cygdrive/c/embedded/workarm/sample320/C:/embedded/workarm/s ample320;C:/embedded/workarm/sample320/.settings;C:/embedded /workarm/sample320/Cfg-Debug-FLASH;C:/embedded/workarm/sampl e320/Cfg-Debug-FLASH/lib;C:/embedded/workarm/sample320/Cfg-D ebug-FLASH/src;C:/embedded/workarm/sample320/Cfg-Debug-XRAM; C:/embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C:/embedded /workarm/sample320/Cfg-Debug-XRAM/src;C:/embedded/workarm/sa mple320/inc;C:/embedded/workarm/sample320/lib;C:/embedded/wo rkarm/sample320/src;C:$cdir:$cwd "
(gdb)
10 info threads
&"info threads\n"
~"* 1 thread 1 (1230) 0x40000020 in start ()\n"
10^done
(gdb)
11-data-list-register-names
11^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)
12-break-insert -t main
12^done,bkpt={number="1",type="breakpoint",disp="del",enabled= "y",addr="0x80000318",func="main",file="../src/main.c",line= "90",times="0"}
(gdb)
13-exec-run
13^running
(gdb)
&"Don't know how to run. Try \"help target\".\n"
13^error,msg="Don't know how to run. Try \"help target\"."
(gdb)
14 info program
Don't know how to run. Try "help target".
&"info program\n"
~"The program being debugged is not being run.\n"
14^done
(gdb)
15 info threads
&"info threads\n"
&"No registers.\n"
15^done
(gdb)
16-stack-info-depth
&"No registers.\n"
16^error,msg="No registers."
(gdb)
17-stack-info-depth
No registers.
&"No registers.\n"
17^error,msg="No registers."
(gdb)
18-data-list-changed-registers
No registers.
No registers.
&"No registers.\n"
18^error,msg="No registers."
(gdb)
19-stack-info-depth
&"No registers.\n"
No registers.
19^error,msg="No registers."
(gdb)
20-stack-info-depth
&"No registers.\n"
No registers.
20^error,msg="No registers."
(gdb)
|
|
|
| Re: uncommon paths gdb Console log file [message #173059 is a reply to message #173037] |
Mon, 17 July 2006 09:19  |
| Eclipse User |
|
|
|
Originally posted by: dmsubs.NOSPAM.consertum.com
Efim,
I think you are getting this problem because you need to specify the
target and 'load' the program into it. Eclipse does not do this for you
as it assumes host-based debugging.
Another problem is that the GDB startup is dependent on your debug
hardware. For example, you could be debugging on a simulator, or through
an ICE, such as Macraigors 'wiggler'. Each will need a different startup.
The first thing you need to do, is work out what your debugger startup
sequence is for your particular configuration. It is best to do this
with the command line debugger. For example, if you are using GDB's
built-in simulator, your startup will look something like this:
target sim
load
run
If you are connecting to a Macraigor wiggler, your startup might look
something like this
target remote :8888
load
run
The 'target' command instructs GDB which debug target to use. The 'load'
command will cause GDB to 'download' the program into the debug target.
The 'run' command instructs GDB to start running the application - it
will normally have set a breakpoint on main() and so will stop when it
hits that breakpoint.
There may well be other commands you need to run as well. Consult your
documentation to find out!
The good news is that you can do this with Eclipse, in a number of ways.
1. Manually
This is the least nice way, but it works. You start a debug session (as
you have done below), and get all of the error messages. Then, find the
GDB console in Eclipse (it will be in the "Console" tab, but remember
that this is a 'stack' of Consoles - you will need to find the correct one).
In the GDB console window, type your startup commands (e.g. target sim
etc.). You should find that your application will now run to the
breakpoint on main().
2. Semi-automatically
Put your startup commands into a gdb .ini file and select that file as
the "GDB Command file" in the Debugger tab of your launch configuration.
Unfortunately, I have found that if you add 'run' to this command file,
your program will just run, without hitting any breakpoints. Therefore,
you will need to enter 'run' manually as in #1 above.
3. Mostly-automatically.
For this, you will need the Zylin Embedded CDT enhancement (as modified
by me). This creates a new launch configuration type 'Embedded CDT',
which allows you to enter your startup commands and 'run' command in 2
separate entry fields, and these are automatically run at the
appropriate times. Go to http://www.zylin.com and look for the Eclipse
Embedded CDT enhancements (I would give you the direct link, but the
website is not working at the moment...)
HTH
---
Derek
efim wrote:
> Hi all,
>
> depend on one of postings in this newsgroup I have changed in the file
> C:\Programme\ARM-Eclipse\plugins\org.eclipse.cdt.debug.mi.co re_3.1.0.200606261600
>
> \plugin.xml cpu settings to "*" because I have had error "CPU not
> supported" if arm-elf-gdb was used.
>
> The error is away but if I try to start the debugger it kills the debug
> session with error:
> Execution is suspended because of error.
> Don't know how to run. Try "help target".
>
> I have logged the communication to gdb as described in CDT FAQ and used
> the verbose CDT console output in CDT. Both outputs are similar as
> expected.
>
> The paths in environment-directory and warnings after it seems unusual
> to me.
> I am using windows and arm-elf-gdb. I can debug this application with
> the same GDB as Console but not in Eclipse.
>
> Does anyone about this problem?
>
> Hier the log from GDB Console:
>
> 1-gdb-set confirm off
> 1^done,address="0x40000020",load-size="2446",transfer-rate= "179522",write-rate="815"
>
> (gdb) 2-gdb-set width 0
> 2^done
> (gdb) 3-gdb-set height 0
> 3^done
> (gdb) 4-interpreter-exec console echo
> 4^done
> (gdb) 5-gdb-show prompt
> 5^done,value="(gdb) "
> (gdb) 6-gdb-set new-console
> &"No symbol \"new\" in current context.\n"
> No symbol "new" in current context.
> 6^error,msg="No symbol \"new\" in current context."
> (gdb) 7-gdb-set new-console
> &"No symbol \"new\" in current context.\n"
> 7^error,msg="No symbol \"new\" in current context."
> (gdb) 8-environment-cd C:\\embedded\\workarm\\sample320
> No symbol "new" in current context.
> 8^done
> (gdb) 9-environment-directory C /embedded/workarm/sample320;C
> /embedded/workarm/sample320/.settings;C
> /embedded/workarm/sample320/Cfg-Debug-FLASH;C
> /embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C
> /embedded/workarm/sample320/Cfg-Debug-FLASH/src;C
> /embedded/workarm/sample320/Cfg-Debug-XRAM;C
> /embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C
> /embedded/workarm/sample320/Cfg-Debug-XRAM/src;C
> /embedded/workarm/sample320/inc;C /embedded/workarm/sample320/lib;C
> /embedded/workarm/sample320/src;C
> &"Warning: /embedded/workarm/sample320/src;C: No such file or directory.\n"
> Warning: /embedded/workarm/sample320/src;C: No such file or directory.
> &"Warning: /embedded/workarm/sample320/lib;C: No such file or directory.\n"
> Warning: /embedded/workarm/sample320/lib;C: No such file or directory.
> &"Warning: /embedded/workarm/sample320/inc;C: No such file or directory.\n"
> Warning: /embedded/workarm/sample320/inc;C: No such file or directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/src;C: No such file
> or directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C: No such file
> or directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM;C: No such file or
> directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/src;C: No such file
> or directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C: No such file
> or directory.
> Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH;C: No such file or
> directory.
> Warning: /embedded/workarm/sample320/.settings;C: No such file or
> directory.
> Warning: /embedded/workarm/sample320;C: No such file or directory.
> Warning: /cygdrive/c/embedded/workarm/sample320/C: No such file or
> directory.
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/src;C: No such
> file or directory.\n"
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C: No such
> file or directory.\n"
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-XRAM;C: No such file or
> directory.\n"
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/src;C: No such
> file or directory.\n"
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH/lib;C: No such
> file or directory.\n"
> &"Warning: /embedded/workarm/sample320/Cfg-Debug-FLASH;C: No such file
> or directory.\n"
> &"Warning: /embedded/workarm/sample320/.settings;C: No such file or
> directory.\n"
> &"Warning: /embedded/workarm/sample320;C: No such file or directory.\n"
> &"Warning: /cygdrive/c/embedded/workarm/sample320/C: No such file or
> directory.\n"
> 9^done,source-path=" /cygdrive/c/embedded/workarm/sample320/C:/embedded/workarm/s ample320;C:/embedded/workarm/sample320/.settings;C:/embedded /workarm/sample320/Cfg-Debug-FLASH;C:/embedded/workarm/sampl e320/Cfg-Debug-FLASH/lib;C:/embedded/workarm/sample320/Cfg-D ebug-FLASH/src;C:/embedded/workarm/sample320/Cfg-Debug-XRAM; C:/embedded/workarm/sample320/Cfg-Debug-XRAM/lib;C:/embedded /workarm/sample320/Cfg-Debug-XRAM/src;C:/embedded/workarm/sa mple320/inc;C:/embedded/workarm/sample320/lib;C:/embedded/wo rkarm/sample320/src;C:$cdir:$cwd "
>
> (gdb) 10 info threads
> &"info threads\n"
> ~"* 1 thread 1 (1230) 0x40000020 in start ()\n"
> 10^done
> (gdb) 11-data-list-register-names
> 11^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) 12-break-insert -t main
> 12^done,bkpt={number="1",type="breakpoint",disp="del",enabled= "y",addr="0x80000318",func="main",file="../src/main.c",line= "90",times="0"}
>
> (gdb) 13-exec-run
> 13^running
> (gdb) &"Don't know how to run. Try \"help target\".\n"
> 13^error,msg="Don't know how to run. Try \"help target\"."
> (gdb) 14 info program
> Don't know how to run. Try "help target".
> &"info program\n"
> ~"The program being debugged is not being run.\n"
> 14^done
> (gdb) 15 info threads
> &"info threads\n"
> &"No registers.\n"
> 15^done
> (gdb) 16-stack-info-depth
> &"No registers.\n"
> 16^error,msg="No registers."
> (gdb) 17-stack-info-depth
> No registers.
> &"No registers.\n"
> 17^error,msg="No registers."
> (gdb) 18-data-list-changed-registers
> No registers.
> No registers.
> &"No registers.\n"
> 18^error,msg="No registers."
> (gdb) 19-stack-info-depth
> &"No registers.\n"
> No registers.
> 19^error,msg="No registers."
> (gdb) 20-stack-info-depth
> &"No registers.\n"
> No registers.
> 20^error,msg="No registers."
> (gdb)
>
|
|
| |
| Re: uncommon paths gdb Console log file [message #173083 is a reply to message #173076] |
Mon, 17 July 2006 12:56 |
| Eclipse User |
|
|
|
Originally posted by: dmsubs.NOSPAM.consertum.com
Efim,
I'm afraid I have not yet got around to trying 3.2.0/3.1.0, (Callista)
so I can't help any more at the moment. It's on my todo list!
However, I would suggest looking at the Embedded CDT enhancements
provided at www.zylin.com - also look at the mail list and maybe post
questions there. I know that Zylin have this working for Callista.
---
Derek
efim wrote:
> Derek,
>
> thank you for responce.
> I have used the 2. method you described. I have an gdb.ini file with
> commandos for GDB which describe target and other parameter to start the
> debugger.
> It works OK with Eclipse 3.1.1 and CDT 3.0.2.
>
> But after I updated to Eclipse 3.2.0 and CDT 3.1.0 the konfiguration
> worked no more.
> At first if I tried to select the debugger I seen error from CDT "CPU is
> not supported" bei all selections exept server GDB. I have asked about
> this in the newsgroup. In one of early messages I have found how the CPU
> check can be switched off. Now it is possible to select any GDB
> konfiguration, but after launching the debugger it kills the debug
> session with error message "don't know how to run". Now it is to solve
> this problem.
>
> I am not sure the warnings about files and paths are not found cause
> this error. But the form in which the paths are written is not a window
> form. You can see it in the log data. Possible I have changed the xml
> file in wrong way, I hope not. Possible they are other CDT settings
> which must be changed.
>
> I think project paths have nothing to do with particular debugger and
> particular target. But I don't know CDT internals.
>
> efim
>
>
>
>
--
Derek
|
|
|
Goto Forum:
Current Time: Sun Jul 27 02:54:47 EDT 2025
Powered by FUDForum. Page generated in 0.24273 seconds |
Home