[#6896] devonshire: toolchain fails to finish running gdb testing on bf609-0.0

Document created by Aaronwu Employee on Oct 17, 2013
Version 1Show Document
  • View in full screen mode

[#6896] devonshire: toolchain fails to finish running gdb testing on bf609-0.0

Submitted By: Mingquan Pan

Open Date

2011-11-23 01:33:31    

Priority:

Medium High     Assignee:

Jim Adams

Jie Zhang

Board:

N/A     Silicon Revision:

Resolution:

Assigned (Not Started)     Fixed In Release:

N/A

Processor:

ALL     

Host Operating System:

toolchain rev.:

    kernel rev.:

State:

Open     Found In Release:

N/A

Is this bug repeatable?:

N/A     

Summary: devonshire: toolchain fails to finish running gdb testing on bf609-0.0

Details:

 

devonshire: toolchain gdbproxy fails to finish running gdb testing on bf609-0.0 .

 

The toolchain is built from:

 

test@adsl:~/344/toolchain/buildscript> /home/test/temp-devon/bfin-elf/bin/bfin-elf-gcc -v

Using built-in specs.

Target: bfin-elf

Configured with: /home/test/344/toolchain/gcc-4.3/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=bfin-elf --prefix=/home/test//temp-devon/bfin-elf --disable-libstdcxx-pch --enable-languages=c,c++ --with-newlib --enable-clocale=generic --disable-symvers --disable-libssp --disable-libffi --disable-libgcj --enable-version-specific-runtime-libs --enable-__cxa_atexit --with-bugurl=URL:http://blackfin.uclinux.org/gf/project/toolchain/tracker --with-pkgversion=ADI-devonshire-trunk/git-f569a6f

Thread model: single

gcc version 4.3.5 (ADI-devonshire-trunk/git-f569a6f)

 

 

Testing command is like:

./toolchain-regtest -s ~/344/toolchain -o /home/test/temp-devon/bfin -b /home/test//temp/regtest_build43.1122 -t elf-jtag -a -L

 

gdbproxy is starting ok, but when the testing comes to gdb, some error info is printed and testing stucks:

...

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] EMUIN pin was asserted: PC [0xC800177E] FP [0xFF700FF4]

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8000B4E] FP [0xFFB00EE4]

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin: [0] a double fault has occured EMUPC [0xFF600000]

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8000F9E] FP [0xFFB00EE4]

error:     bfin: [0] CORE FAULT core cannot read register [53]

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      [0] core fault: DBGSTAT [0x4058]

info:      Resetting ...

info:      [1] forced to halt

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin: [0] EMUEXCPT instruction was executed: PC [0xFF6001AA] FP [0xFF700FC8]

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8000F9E] FP [0xFFB00EE4]

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK 250MHz

info:      bfin: [0] EMUIN pin was asserted: PC [0xFF600126] FP [0xFF700FC8]

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8000FA0] FP [0xFFB00EE4]

bfin-gdbproxy: /home/test/344/toolchain/urjtag/src/bfin/bfin.c:373: part_check_emuready: Assertion `emuready' failed.

Aborted

adsl:/home/test/temp-devon/bfin-elf/bin #

 

 

The gdb.log is like:

Running /home/test/344/toolchain/binutils-2.17/gdb/testsuite/gdb.gdbtk/c_variable.exp ...

spawn Xvfb :1969 -ac^M

Executing on host: bfin-elf-gcc /home/test/344/toolchain/binutils-2.17/gdb/testsuite/gdb.gdbtk/c_variable.c   -mcpu=bf609-0.0    -g  -lm  -mcpu=bf609-0.0  -o /home/test/temp/regtest_build43.1122/gdb_build/testsuite/gdb.gdbtk/c_variable    (timeout = 300)

spawn bfin-elf-gcc /home/test/344/toolchain/binutils-2.17/gdb/testsuite/gdb.gdbtk/c_variable.c -mcpu=bf609-0.0 -g -lm -mcpu=bf609-0.0 -o /home/test/temp/regtest_build43.1122/gdb_build/testsuite/gdb.gdbtk/c_variable^M

 

==== c_variable-1.1 create global variable

==== Contents of test case:

 

  create_variable global_simple

 

==== Result was:

0

++++ c_variable-1.1 PASSED

 

 

==== c_variable-1.2 create non-existent variable

==== Contents of test case:

 

  create_variable bogus_unknown_variable

 

==== Result was:

1

++++ c_variable-1.2 PASSED

 

 

==== c_variable-1.3 create out of scope variable

==== Contents of test case:

 

  create_variable argc

 

==== Result was:

1

++++ c_variable-1.3 PASSED

                                                                

 

 

 

Follow-ups

 

--- Stuart Henderson                                         2011-11-30 10:45:20

Is there a specific reason this has been assigned to me?  it looks like it's in

Jie's domain.

 

--- Sonic Zhang                                              2011-11-30 21:44:34

OK. Assign to Jie.

 

--- Jie Zhang                                                2011-12-01 22:49:37

What are the gdbproxy options? What's the boot mode?

 

--- Mingquan Pan                                             2011-12-06 22:12:33

The gdb proxy starts like:

Starting start_gdbproxy.exp

 

************** STEP 1: Run start gdbproxy.

 

spawn su^M

Password: ^M

^[[1m^[[31madsl:/home/test/temp-devon/bfin-elf/bin # ^[(B^[[msu success.

ps aux| grep bfin-gdbproxy | grep -v grep^M

^[[1m^[[31madsl:/home/test/temp-devon/bfin-elf/bin # ^[(B^[[m./bfin-gdbproxy

bfin^M

^M

Remote proxy for GDB, v0.7.2, Copyright (C) 1999 Quality Quorum Inc.^M

MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood^M

Blackfin adaption Copyright (C) 2008 Analog Devices, Inc.^M

^M

GDBproxy comes with ABSOLUTELY NO WARRANTY; for details^M

use `--warranty' option. This is Open Source software. You are^M

welcome to redistribute it under certain conditions. Use the^M

'--copying' option for details.^M

^M

Found USB cable: gnICE^M

Connected to libftdi driver.^M

IR length: 5^M

Chain length: 1^M

Device Id: 00000010100000000100000011001011 (0x028040CB)^M

  Manufacturer: Analog Devices, Inc. (0x0CB)^M

  Part(0):      SDU (0x2804)^M

  Stepping:     0^M

  Filename:     ./../share/urjtag/analog/sdu/sdu^M

warning:   bfin: no board selected, 3 parts are detected^M

warning:   bfin:   parts: [BF609 BF609] SDU ^M

notice:    bfin: jc: waiting on TCP port 2001^M

notice:    bfin: jc:  (you must connect GDB before using jtag console)^M

notice:    bfin-gdbproxy: waiting on TCP port 2000^M

GDBproxy is already been started.notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin: [1] core is in idle mode^M

info:      bfin: [0] EMUEXCPT instruction was executed: PC [0xFF60279E] FP

[0xFF700F2C]^M

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8001020] FP [0xFFB00E90]^M

info:      bfin-gdbproxy: session killed. Will wait for a new connection^M

notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin: [0] EMUEXCPT instruction was executed: PC [0xFF60279E] FP

[0xFF700F2C]^M

info:      bfin: [1] EMUIN pin was asserted: PC [0xC8001020] FP [0xFFB00E90]^M

info:      bfin-gdbproxy: session killed. Will wait for a new connection^M

notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin-gdbproxy: session killed. Will wait for a new connection^M

notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin-gdbproxy: session killed. Will wait for a new connection^M

notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin-gdbproxy: session killed. Will wait for a new connection^M

notice:    bfin-gdbproxy: connected^M

info:      bfin: CCLK 500MHz SCLK 250MHz S0CLK 125MHz S1CLK 125MHz DCLK

250MHz^M

info:      bfin: [0] EMUIN pin was asserted: PC [0xFF6000C4] FP [0xFF700F2C]^M

 

 

And what do you mean by boot mode? The bf609 ezkit board? it doesn't have uboot

and didn't boot up.

 

--- Jie Zhang                                                2011-12-06 22:35:52

Yes, I meant the boot mode of bf609 ezkit board.

 

--- Jie Zhang                                                2011-12-13 16:09:15

I just fixed a bug in gdbproxy which I found on Windows host. But it should also

affect Linux host. I'm not sure if it's the same bug. But it's worth to try.

Please update gdbproxy from the latest devonshire-trunk and redo the testing.

 

--- Mingquan Pan                                             2012-06-06 23:24:18

I try recently gdbproxy test on bf609-ezkit with 2012R1-BETA1 toolchain, but it

looks the resluts remains the same. Gdb testing is very slow and finally stucks

at gdb.gdbtk/c_variable.exp.

the bf609 ezkit board is switched to 1 which is parallel flash boot mode, but

this board is of version 0.3 and can't start up with this boot mode.

 

the log is:

==== Result was:

2

++++ c_variable-4.76 PASSED

 

 

==== c_variable-4.77 children of struct_declarations.s2.u2.u1s2.func

==== Contents of test case:

 

  get_children struct_declarations.s2.u2.u1s2.func

 

==== Result was:

 

++++ c_variable-4.77 PASSED

 

 

==== c_variable-4.78 number of children of struct_declarations.s2.u2.u1s2.func

==== Contents of test case:

 

  $var(struct_declarations.s2.u2.u1s2.func) numChildren

 

==== Result was:

0

++++ c_variable-4.78 PASSED

 

 

==== c_variable-4.79 children of struct_declarations.*int_ptr_ptr

==== Contents of test case:

 

  get_children struct_declarations.int_ptr_ptr.*int_ptr_ptr

 

==== Result was:

**int_ptr_ptr

++++ c_variable-4.79 PASSED

 

 

==== c_variable-4.80 Number of children of struct_declarations.*int_ptr_ptr

==== Contents of test case:

 

  $var(struct_declarations.int_ptr_ptr.*int_ptr_ptr) numChildren

 

==== Result was:

1

++++ c_variable-4.80 PASSED

"~/temp/regtest_build43.0606/gdb_build/testsuite/gdb.log" 45786L,

2338502C                                                                       

                                         45786,1       Bot

 

and when testing is stuck at elf-jtag gdb testing, the coreb is in idle mode

like:

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

info:      bfin: [0] core is in idle mode

 

 

--- Jie Zhang                                                2012-06-06 23:53:44

You can add --bf609-bmode1-workaround to gdbproxy to work around the boot issue.

 

--- Mingquan Pan                                             2012-06-08 04:26:13

I can have a try with this --bf609-bmode1-workaround, but actually bfin-gdbproxy

connects this board is ok without problem. when I say "the board can't

start up with this boot mode", I mean we didn't use parralel boot mode on

this board, instead we use spi flash boot.

 

but, anyway, elf-jtag testing doesn't require board to be started in u-boot,

isn't it? So it should not matter what boot mode is used?

 

--- Sonic Zhang                                              2012-07-04 01:06:53

After 2 hour continuous testing, the bfin-elf-gdb fails to load and run dejaGNU

test case gdb.cp/ref-params via gdbproxy on bf609-ezkit. But, if you reset the

bf609 board and run the same test individually, it can pass. This looks like

bf609 is in bad status after runs a bunch of tests via gdb/gdbproxy.

 

Test log:

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

Continuing.

FAIL: gdb.cp/ref-params.exp: running to ref-params.cc:71 in runto (timeout)

print Q

FAIL: gdb.cp/ref-params.exp: print value of a Child in main (timeout)

print f1(Q)

FAIL: gdb.cp/ref-params.exp: print value of f1 on Child in main (timeout)

print f2(Q)

FAIL: gdb.cp/ref-params.exp: print value of f2 on Child in main (timeout)

dir

kill

file

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

ERROR: couldn't load

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

into bfin-elf-gdb (timed out).

delete breakpoints

ERROR: Delete all breakpoints in delete_breakpoints (timeout)

break ref-params.cc:71

UNRESOLVED: gdb.cp/ref-params.exp: setting breakpoint at ref-params.cc:71

(timeout)

print f1(QR)

FAIL: gdb.cp/ref-params.exp: print value of f1 on (Child&) in main

(timeout)

dir

kill

file

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

ERROR: couldn't load

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

into bfin-elf-gdb (timed out).

delete breakpoints

ERROR: Delete all breakpoints in delete_breakpoints (timeout)

break ref-params.cc:71

UNRESOLVED: gdb.cp/ref-params.exp: setting breakpoint at ref-params.cc:71

(timeout)

print f2(QR)

FAIL: gdb.cp/ref-params.exp: print value of f2 on (Child&) in main

(timeout)

dir

kill

file

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

ERROR: couldn't load

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

into bfin-elf-gdb (timed out).

delete breakpoints

ERROR: Delete all breakpoints in delete_breakpoints (timeout)

break ref-params.cc:39

UNRESOLVED: gdb.cp/ref-params.exp: setting breakpoint at ref-params.cc:39

(timeout)

print C

FAIL: gdb.cp/ref-params.exp: print value of Child& in f2 (timeout)

print f1(C)

FAIL: gdb.cp/ref-params.exp: print value of f1 on Child& in f2 (timeout)

dir

kill

file

/home/sonic/projects/toolchain/buildscript/temp/gdb_build/testsuite/gdb.cp/ref-params

 

 

gdbproxy log:

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

info:      bfin: [0] EMUIN pin was asserted: PC [0xFF600006] FP [0xFF700FBC]

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

info:      bfin-gdbproxy: session killed. Will wait for a new connection

notice:    bfin-gdbproxy: connected

 

 

--- Mingquan Pan                                             2012-08-02 05:38:24

I try elf-jtag testing with your latest checkins in toolchain, finding that the

testing results gets better now and gcc, g++ can finish test with decent

results, but gdb testing remains stuck as before.

 

************** Testing is done on target with kernel config (normal).

*************

************** Testing 4.3 toolchain on NON_EXIST. ************

************** Host UBUNTU 10.99.29.100. ***********

 

************** Tested toolchain svn info ***************

At revision 5891.

Path: .

URL: svn://10.99.22.20/toolchain/trunk

Repository Root: svn://10.99.22.20/toolchain

Repository UUID: 2adf4935-75e9-4407-93b2-34b21a1880a4

Revision: 5891

Node Kind: directory

Schedule: normal

Last Changed Author: jiez

Last Changed Rev: 5891

Last Changed Date: 2012-08-01 09:26:27 +0800 (Wed, 01 Aug 2012)

************** Tested U-Boot git info ******************

U-Boot Already up-to-date.

origin  git://10.99.22.20/git/u-boot (fetch)

origin  git://10.99.22.20/git/u-boot (push)

* trunk

  remotes/origin/2005R1

  remotes/origin/2005R2

...

 

+ ./toolchain-regtest -s /home/test/workspace/src/toolchain -o

/home/test/temp/bfin -b /home/test/temp/regtest_build4.3 -t elf-jtag -a -L !gdb

Targets:                    elf-jtag

Components:                 binutils gas ld sim newlib gcc g++ gfortran objc

libstdc++ libmudflap libgomp

Host:                       i686-pc-linux-gnu

Build:                      i686-pc-linux-gnu

Removing from PATH: /opt/uClinux/bfin-uclinux/bin

Removing from PATH: /opt/uClinux/bfin-elf/bin

Removing from PATH: /opt/uClinux/bfin-linux-uclibc/bin

Toolchain source:           /home/test/workspace/src/toolchain

Path to logs output dir:    /home/test/temp/regtest_build4.3/logs

Path to tests output dir:   /home/test/temp/regtest_build4.3/tests

Path to elf-jtag output dir: /home/test/temp/regtest_build4.3/tests/elf-jtag

Previous elf-jtag test logs:

/home/test/workspace/src/toolchain/buildscript/test_results/elf-jtag

Creating log file:          /home/test/temp/regtest_build4.3/logs/log

*** Found old processes (Xvfb); killing them to avoid       02 Aug 2012

03:03:41

    confusing the testsuites

Path to boards output dir:  /home/test/temp/regtest_build4.3/boards

*** Testing bfin-elf via jtag                               02 Aug 2012

03:03:41

*** Found old processes (Xvfb rsh); killing them to avoid   02 Aug 2012

03:03:41

    confusing the testsuites

binutils version:           2.21

binutils path:              /home/test/temp/bfin-elf/bin

*** Running tests on binutils                               02 Aug 2012

03:03:42

*** Running tests on gas                                    02 Aug 2012

03:11:47

*** Running tests on ld                                     02 Aug 2012

03:11:57

gcc version:                4.3.5

gcc path:                   /home/test/temp/bfin-elf/bin

*** Running tests on gcc                                    02 Aug 2012

03:12:16

*** Running tests on g++                                    02 Aug 2012

03:36:44

bfin-elf-gfortran not found

objc support not found in bfin-elf toolchain

*** Running tests on libstdc++                              02 Aug 2012

03:44:22

*** Running tests on newlib                                 02 Aug 2012

04:07:37

*** Legacify result names                                   02 Aug 2012

04:07:39

*** Done testing - results                                  02 Aug 2012

04:07:39

 

### New: binutils-2.21.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === binutils Summary ===

# of expected passes            74

# of unresolved testcases       3

# of unsupported tests          5

### New: g++-4.3.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === g++ Summary ===

# of expected passes            15935

# of unexpected failures        1

# of expected failures          160

# of unresolved testcases       98

# of untested testcases         1304

# of unsupported tests          185

 

### New: gas-2.21.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === gas Summary ===

# of expected passes            160

# of expected failures          1

 

### New: gcc-4.3.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === gcc Summary ===

# of expected passes            39600

# of unexpected failures        6

# of expected failures          90

# of unresolved testcases       67

# of untested testcases         9602

# of unsupported tests          454

 

### New: ld-2.21.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === ld Summary ===

# of expected passes            183

# of expected failures          9

 

### New: libstdc++-4.3.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === libstdc++ Summary ===

# of expected passes            1826

# of expected failures          1023

# of unresolved testcases       959

# of untested testcases         773

# of unsupported tests          521

 

### New: newlib-4.3.sum in /home/test/temp/regtest_build4.3/tests/elf-jtag

                === newlib Summary ===

# of expected passes            12

# of unexpected failures        1

# of unresolved testcases       4

# of untested testcases         7

 

*** It took 1h3m58s to complete                             02 Aug 2012

04:07:39

+ find /home/test/temp/regtest_build4.3/. -maxdepth 1 -type d -regex

.*build[-0-9.]* -exec mv {} {}-elf-jtag ;

+ ./toolchain-regtest -s /home/test/workspace/src/toolchain -o

/home/test/temp/bfin -b /home/test/temp/regtest_build4.3 -t elf-jtag -a -L gdb

Targets:                    elf-jtag

Components:                 gdb

Host:                       i686-pc-linux-gnu

Build:                      i686-pc-linux-gnu

Removing from PATH: /opt/uClinux/bfin-uclinux/bin

Removing from PATH: /opt/uClinux/bfin-elf/bin

Removing from PATH: /opt/uClinux/bfin-linux-uclibc/bin

Toolchain source:           /home/test/workspace/src/toolchain

Path to logs output dir:    /home/test/temp/regtest_build4.3/logs

Path to tests output dir:   /home/test/temp/regtest_build4.3/tests

Path to elf-jtag output dir: /home/test/temp/regtest_build4.3/tests/elf-jtag

Previous elf-jtag test logs:

/home/test/workspace/src/toolchain/buildscript/test_results/elf-jtag

Creating log file:          /home/test/temp/regtest_build4.3/logs/log

Path to boards output dir:  /home/test/temp/regtest_build4.3/boards

*** Testing bfin-elf via jtag                               02 Aug 2012

04:07:40

gdb version:                6.6

gdb path:                   /home/test/temp/bfin-elf/bin

*** Running tests on gdb                                    02 Aug 2012

04:07:40

 

It still stucks here and not going on.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

gdb.log.gz    application/x-gzip    209034    Mingquan Pan

Attachments

Outcomes