[prev in list] [next in list] [prev in thread] [next in thread]
List: ecos-bugs
Subject: [Bug 1000699] New: New Platform template
From: bugzilla-daemon () ecoscentric ! com
Date: 2009-02-26 10:36:01
Message-ID: bug-1000699-13 () http ! bugs ! ecos ! sourceware ! org/
[Download RAW message or body]
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000699
Summary: New Platform template
Product: eCos
Version: 3.0beta1
Platform: Other (please specify)
OS/Version: HostOS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: ConfigTool
AssignedTo: john@dallaway.org.uk
ReportedBy: sergei.gavrikov@gmail.com
QAContact: ecos-bugs@ecos.sourceware.org
Class: ---
Created an attachment (id=650)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=650)
ConfigTool: Run Tests output.
When we create new platform template, the default GDB arguments are
----------------------------->8
set height 0
set debug remote 0
set remotebaud %b
target remote %p
load
break cyg_test_exit
rbreak cyg_assert_fail
break cyg_test_init
cont
set cyg_test_is_simulator=0
cont
bt
----------------------------->8
What is about
'bt COUNT' on the last line?
I do not know what is enough for eCos tests: 16, 32, or 64... Why I ask about
the limit? Testing eCos 3.0 beta 1 on Olimex LPC-H2294 target I met a situation
when I ran kernel/tests/except1 (test passed successfully), and a batch run was
stopped because arm-eabi-gdb did an infinitive back tracing (see an attachment,
please).
Do you need in the COUNT in the GDB arguments template? Well, perhaps, it is
issue for my platform only. Then forget it, please.
Thanks for your comments.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic