This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1000699] except1 test: infinite backtrace on ARM


http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000699


John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john@dallaway.org.uk
         AssignedTo|john@dallaway.org.uk        |jifl@ecoscentric.com
           Severity|enhancement                 |normal
          Component|ConfigTool                  |Debugging
           Priority|low                         |normal
            Summary|New Platform template       |except1 test: infinite
                   |                            |backtrace on ARM
               Flag|                            |Blocking_3.0?




--- Comment #2 from John Dallaway <john@dallaway.org.uk>  2009-02-26 11:23:54 ---
I am most concerned about the infinite backtrace from GDB with the except1
test. This is also seen in the test farm on AT91EB40A and IXDP425 but not on
other (non-ARM) architectures.

Jifl, do we need to add one of the eCos exception handler functions to the list
of known thread entry points in GDB or is there another solution/explanation?

Moving to the "Debugging" component for now.


-- 
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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]