Re: [ECOS] Re: How to set GDB Stub Options in order to run insight ?

["m mariga" <ma_ariga@yahoo.co.jp>]

Hello,

I am very sorry for my ambiguity.
Please make allowance for my poor capacity of English.

What I am doing is only to confirm the operation of Insight debugging 
application(nc_test_slave.elf).
My purpose is that I start up Insight on cygwin and load nc_test_slave.elf 
and know it breaks at top of cyg_start and I can do stepping operation.

Since I changed <CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS> option to 1,Insight 
began to display log strings when I entered "c"(continue),
but it still  can't go to break-point at top of cyg_start and bogged in 
silence state after displaying [cyg_net_init] Done.

I only showed normal RedBoot-log for comparing in order to know the cause of 
Insight's stopping.
This was the log that I ran nc_test_slave on RedBoot-Monitor by "go" command 
without Insight.
I deducted that Insight-stopping's cause is related to network operation 
because on RedBoot-log,"Start Network Characterization - SLAVE" was 
displayed after [cyg_net_init] Done.
My guessing is that I perhaps could be able to run through Insight by making 
network-related options available.
I beseech you to teach me that.

After I changed <CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS> option to 1,I re-ran 
newly-built nc_test_slave on RedBoot-Monitor without Insight by way of 
trial.
Then it failed by displaying next codes,whereas on previous normal 
RedBoot-log it showed "Network stack using 69632 bytes for misc space" .

RedBoot> go 0x410000
$O4E6574776F726B20737461636B207573696E6720363936333220627974657320666F72206D6973632073706163650A#0C

I strengthened my network-related guessing because network function was 
deteriorated by my changing <CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS> option to 
1.

By the way in order to not use BOOTP,I have been making 
CYGSEM_REDBOOT_DEFAULT_NO_BOOTP option available in redboot.cdl.

From here on, my explanation is vagued by bad memory.
About 2 years ago,I succeeded to ran the same nc_test_slave on SH target 
using Insight.
I confirmed I could step through the source codes,so I could debug network 
program on Insight.
At that time,I think I did not change CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS to 
1,so maybe there are other ways to run nc_test_slave on Insight not by 
manipulating CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS option.
I am not sure.

I am much obliged your help.

m mariga


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss