Re: Re: problems about the mcore-elf-gdb

["William A. Gatliff" <bgat at saturn dot open-widgets dot com>]

You don't have something important like, say, your stub's stack frame,
located around 8100C000B, do you?

:^)


b.g.

On Fri, Jul 05, 2002 at 02:43:44PM +0800, leiming wrote:
> 
>  Hi!
>  I have set debug remote 1 in the mcore-gdb console hosted in cygwin.The result follows and please help me analysis it
> 
> (gdb) set debug remote 1
> (gdb) target picobug com1
> read -->\n<--
> read -->\r<--
> read -->picobug> nobr\n<--
> read -->\r<--
> read -->picobug> Remote target picobug connected to com1\n<--
> read -->\r<--
> read -->picobug> rd\n<--
> read -->\r<--
> read -->     pc 8100c000      epc 80010a94      fpc 01002005\r\n<--
> read -->    psr 80000000     epsr 80000001     fpsr 08000200\r\n<--
> read -->ss0-ss4 bad0beef 81003000 20000800 00000000 00008100      vbr 81002c00\r\n<--
> read -->  r0-r7 bad0beef 00000000 81003000 80013f90 81001fb4 8001402f 00000014 0
> 0000000\r\n<--
> read --> r8-r15 81000024 80010040 0000000f 810037c9 810037c4 810037c9 81002f94 8
> 0010852\r\n<--
> read -->picobug> 0x8100c000 in ?? ()
> (gdb) load testgnu.elf
> lo\n<--
> sent -->S0030000FC\r.text       : 0x8100c000 .. 0x8100c170  <--
> sent -->S30E8100C000710B12107F0B00002464\r<--
> sent -->S30E8100C009709F008F00207000CFAA\r<--
> sent -->S30E8100C012000024709F008F0020BC\r<--
> sent -->S30E8100C01B7000CF000024709F0023\r<--
> sent -->S30E8100C0248F00207000CF0000811D\r<--
> sent -->S30E8100C02D00F0008100C03424F00A\r<--
> sent -->S30E8100C0369F20983012087F1C2C12\r<--
> sent -->S30E8100C03F8260037F1B60079708EC\r<--
> sent -->S30E8100C048870822A7E001F01560CA\r<--
> sent -->S30E8100C0510260137F177F1760124C\r<--
> sent -->S30E8100C05A60137F157F15602260D9\r<--
> sent -->S30E8100C063137F137F136032601311\r<--
> sent -->S30E8100C06C7F117F118708127620ED\r<--
> sent -->S30E8100C075069608F7E712808F2078\r<--
> sent -->S30E8100C07E883020F000CF24F098EF\r<--
> sent -->S30E8100C0872012086007970887085A\r<--
> sent -->S30E8100C090760A0D76E801F00587B8\r<--
> sent -->S30E8100C09908127620069608F7F6D6\r<--
> sent -->S30E8100C0A21280882020F000CF00F5\r<--
> sent -->S30E8100C0AB008100C0208100C0BCA7\r<--
> sent -->S30E8100C0B48100C0840000C34F2500\r<--
> sent -->S30E8100C0BD70984012081226123710\r<--
> sent -->S30E8100C0C61266B6081277B71877E5\r<--
> sent -->S30E8100C0CF2697186007B7888718C7\r<--
> sent -->S30E8100C0D8A607B688A78812762E08\r<--
> sent -->S30E8100C0E1F61267B788A7082C86C0\r<--
> sent -->S30E8100C0EA0F67E009A7182A17E087\r<--
> sent -->S30E8100C0F30360F7B788F0026007CB\r<--
> sent -->S30E8100C0FCB788F01DA7082A17E890\r<--
> sent -->S30E8100C1050E2217E8032A07E80659\r<--
> sent -->S30E8100C10EF0152A27E80B2A37E80F\r<--
> sent -->S30E8100C1170DF01087186016B607B9\r<--
> sent -->S30E8100C120F00C87186026B607F0C1\r<--
> sent -->S30E8100C1290887186046B607F00488\r<--
> sent -->S30E8100C13287186086B607F0001239\r<--
> sent -->S30E8100C13B808840217000CF24F0B8\r<--
> sent -->S30E8100C144982012087709970887F3\r<--
> sent -->S30E8100C14D08A60712672EE7127697\r<--
> sent -->S30E8100C156B648A74801071212F050\r<--
> sent -->S30E8100C15F001280882020F000CF37\r<--
> sent -->S30D8100C168817FFFFD817FFFFC51\r
> .data   : 0x8100d000 .. 0x8100d000
> .rodata : 0x8100c170 .. 0x8100c170
> <--
> sent -->S7058100C000B9\r<--
> sent -->\r\rTransfer rate: 2944 bits in <1 sec, 368 bytes/write.
> Timeout reading from remote system.
> (gdb)
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  >
>  >> When I run mcore-elf-gdb to debug my mcore-elf program in the
>  >> "target sim" mode,I can get designed result.When I am ready to
>  >> cross-debug the program,I also can connect to the target
>  >> machine(mcore) with the command "target picobug com1",but I can't
>  >> download it to the target machine."Picobug" is the monitor runing in
>  >> the mcore target machine and is supported by the gdb.
>  >> 
>  >> who can help me to solve the problem?
>  >
>  >You can!  :^)
>  >
>  >(gdb) set debug remote 1
>  >
>  >Then try the download again, and take a look at where it bombs out.
>  >That'll give us more of an idea where to look.
>  >
>  >Erp, it just occurred to me that picobug may not do a log file, or may
>  >use a different command to activate it.  Try to figure that out,
>  >because the alternative is for someone to replicate your setup and run
>  >mcore-elf-gdb under gdb...
>  >
>  >
>  >Cheers,
>  >
>  >b.g.
>  >--
>  >Bill Gatliff
>  >bgat@billgatliff.com
>  >
>  >
> 
> ______________________________________
> 
> ===================================================================
> 新浪免费电子邮箱 (http://mail.sina.com.cn)
> 新浪分类信息：二手市场走一走，该出手时就出手！ (http://classad.sina.com.cn/2shou/)

-- 
Bill Gatliff
bgat@billgatliff.com