Eclipse Community Forums: C / C++ IDE (CDT)

Home » Language IDEs » C / C++ IDE (CDT) » cdt gdb memory problem

cdt gdb memory problem [message #160722]

Tue, 20 December 2005 09:06

Eclipse User

Originally posted by: rekisum.ms.de

Hi,
displaying memory from 0x0 works with cdt.
Displaying other adresses doesn't work.
I see only questionmarks as values.
Something like x 0xE0005000 on the gdb command line works!
I use eclipse 3.1 with embedded cdt from zylin.
Loading command doesn't work also, only from gdb script.
Regards,
Joerg

Re: cdt gdb memory problem [message #160755 is a reply to message #160722]

Tue, 20 December 2005 11:59

Eclipse User

Originally posted by: mikhailk.qnx.com

I would suggest to post this message to the Zylin mailing list.

"rekisum" <rekisum@ms.de> wrote in message
news:a459bd492297ac3424f6cd99928bb723$1@www.eclipse.org...
> Hi,
> displaying memory from 0x0 works with cdt.
> Displaying other adresses doesn't work.
> I see only questionmarks as values.
> Something like x 0xE0005000 on the gdb command line works!
> I use eclipse 3.1 with embedded cdt from zylin.
> Loading command doesn't work also, only from gdb script.
> Regards,
> Joerg
>

Re: cdt gdb memory problem [message #160938 is a reply to message #160755]

Thu, 22 December 2005 11:41

Eclipse User

Originally posted by: reksi.web.de

Hi,
I did ask this also at the zylin mailing list.
CDT/Eclipse hangs on the gdb 'load' command.
I checked with two gdb server versions: Wiggler and BDI2000.
Both are connected over target remote IP:Port to gdb.
gdb command line works fine so far, where cdt fails.
This is the log:

[1.135.266.993.267] D:\Programme\sarm\bin\gdb.exe --cd=D:\EigeneDate
eclbdi2 --command=.g\
dbinit -q -nw -i mi D:\EigeneDateien\eclipse\eclbdi2\eclbdi2.elf
[1.135.266.993.267] 77-gdb-set confirm off
[1.135.266.993.283] 77^done
[1.135.266.993.283] (gdb)
[1.135.266.993.283] 78-gdb-set width 0
[1.135.266.993.283] 78^done
[1.135.266.993.283] (gdb)
[1.135.266.993.283] 79-gdb-set height 0
[1.135.266.993.283] 79^done
[1.135.266.993.283] (gdb)
[1.135.266.993.283] 80-interpreter-exec console echo
[1.135.266.993.283] 80^done
[1.135.266.993.283] (gdb)
[1.135.266.993.283] 81-gdb-show prompt
[1.135.266.993.283] 81^done,value="(gdb) "
[1.135.266.993.283] (gdb)
[1.135.266.993.283] 82-stack-list-frames
[1.135.266.993.283] &"No registers.\n"
[1.135.266.993.283] 82^error,msg="No registers."
[1.135.266.993.283] (gdb)
[1.135.266.993.330] 83 target remote 192.168.52.36:2001
[1.135.266.993.345] &"target remote 192.168.52.36:2001\n"
[1.135.266.993.377] ~"_startup () at startup.S:79\n"
[1.135.266.993.377] ~"79\tReset_Vec: B ResetEntry\n"
[1.135.266.993.377] ~"Current language: auto; currently asm\n"
[1.135.266.993.377] 83^done
[1.135.266.993.377] (gdb)
[1.135.266.993.377] 84 load
[1.135.266.993.392] &"load\n"
[1.135.266.993.392] ~"Loading section .text, size 0x29c lma 0x0\n"

And there is stays forever.
Any hints?
I'am missing some file command.
Is gdb started with 'gdb test.elf' or something?
If you need more information, tell me how to get.
Regards,

Heinz

Re: cdt gdb memory problem [message #160952 is a reply to message #160938]

Thu, 22 December 2005 15:10

Eclipse User

Originally posted by: mikhailk.qnx.com

The first three lines show that gdb was started with
"D:\EigeneDateien\eclipse\eclbdi2\eclbdi2.elf."
I don't know how Zylin launcher works, but it looks like gdb hangs during
the "load" command.

"heinz" <reksi@web.de> wrote in message
news:57458991a8d1da24b31b07314844ae0a$1@www.eclipse.org...
> Hi,
> I did ask this also at the zylin mailing list.
> CDT/Eclipse hangs on the gdb 'load' command.
> I checked with two gdb server versions: Wiggler and BDI2000.
> Both are connected over target remote IP:Port to gdb.
> gdb command line works fine so far, where cdt fails.
> This is the log:
>
> [1.135.266.993.267] D:\Programme\sarm\bin\gdb.exe --cd=D:\EigeneDate
> eclbdi2 --command=.g\
> dbinit -q -nw -i mi D:\EigeneDateien\eclipse\eclbdi2\eclbdi2.elf
> [1.135.266.993.267] 77-gdb-set confirm off
> [1.135.266.993.283] 77^done
> [1.135.266.993.283] (gdb)
> [1.135.266.993.283] 78-gdb-set width 0
> [1.135.266.993.283] 78^done
> [1.135.266.993.283] (gdb)
> [1.135.266.993.283] 79-gdb-set height 0
> [1.135.266.993.283] 79^done
> [1.135.266.993.283] (gdb)
> [1.135.266.993.283] 80-interpreter-exec console echo
> [1.135.266.993.283] 80^done
> [1.135.266.993.283] (gdb)
> [1.135.266.993.283] 81-gdb-show prompt
> [1.135.266.993.283] 81^done,value="(gdb) "
> [1.135.266.993.283] (gdb)
> [1.135.266.993.283] 82-stack-list-frames
> [1.135.266.993.283] &"No registers.\n"
> [1.135.266.993.283] 82^error,msg="No registers."
> [1.135.266.993.283] (gdb)
> [1.135.266.993.330] 83 target remote 192.168.52.36:2001
> [1.135.266.993.345] &"target remote 192.168.52.36:2001\n"
> [1.135.266.993.377] ~"_startup () at startup.S:79\n"
> [1.135.266.993.377] ~"79\tReset_Vec: B ResetEntry\n"
> [1.135.266.993.377] ~"Current language: auto; currently asm\n"
> [1.135.266.993.377] 83^done
> [1.135.266.993.377] (gdb)
> [1.135.266.993.377] 84 load
> [1.135.266.993.392] &"load\n"
> [1.135.266.993.392] ~"Loading section .text, size 0x29c lma 0x0\n"
>
> And there is stays forever.
> Any hints?
> I'am missing some file command.
> Is gdb started with 'gdb test.elf' or something?
> If you need more information, tell me how to get.
> Regards,
>
> Heinz
>

Re: cdt gdb memory problem [message #160984 is a reply to message #160952]

Fri, 23 December 2005 04:19

Eclipse User

Originally posted by: heinz.keins.de

hi,

yes, this is what I said.
It hangs on the 'load' command.
But the gdb command line works.
So I wonder if any of the cdt-freaks
around knows a solution, or a reason.
I got no experience in eclipse or java.
By

Previous Topic:	Error parser
Next Topic:	New feature request?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue May 13 19:03:21 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter