From: Ilija Kocho <ilijak@siva.com.mk>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: GCC 4.6 resourcing.
Date: Fri, 27 Jan 2012 14:32:00 -0000 [thread overview]
Message-ID: <4F22B567.4070403@siva.com.mk> (raw)
In-Reply-To: <4F1F265B.2080700@dallaway.org.uk>
Hi John
On 24.01.2012 22:44, John Dallaway wrote:
> Hi Ilija
>
>
> Does the backtrace for an eCos thread and for HAL startup code work
> reliably with GDB 7.3.1? In the past, we have seen issues where the
> backtrace code can enter an infinite loop, hence the patch for GDB 6.8.50.x.
Now I have addressed GDB patches too. Here's the outcome:
File: gdb-6.8.50.20080706.patch
frame.c
eCos backtrace hack.
Wasn't applied, /bt/ didn't stop at /thread_entry/. I did apply all
patches to frame.c and now it seems to work properly (Screen captures
are below).
findvar.c
The patches mention phrase "frame" so I assume they are related to
frame.c patches.
I did apply the patches but my assumption may be wrong. Need
confirmation?
valops.c
Same discussion as for findvar.c
infcall.c
Was up to date.
symtab.c
Was up to date.
dwarf2-frame.c
Code has changed, patch is very likely obsolete.
File: gdb-6.8.50.20080706-arm.patch
The subject sources have been significantly reworked. I could identify
that some patches have been applied and some parts reworked beyond
recognition. Very likely that all patches are obsolete.
----- Screen captures [nc_test_slave]
----------------------------------------
-- Before patch: ----
gdb> bt
#0 do_some_random_computation (p=<optimized out>) at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/net/lwip_tcpip/current/tests/nc_test_slave.c:684
#1 net_load (who=<optimized out>) at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/net/lwip_tcpip/current/tests/nc_test_slave.c:668
#2 0x000033be in Cyg_HardwareThread::thread_entry (thread=0x1fff28d8)
at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/kernel/current/src/common/thread.cxx:94
#3 0x00003b7a in Cyg_Scheduler::start_cpu () at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/kernel/current/src/sched/sched.cxx:402
#4 0x000033ac in reschedule () at
/home/vae/Proekti/pd/sem/ecos_kinetis/lwip_test_install/include/cyg/kernel/sched.inl:114
#5 Cyg_Thread::exit () at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/kernel/current/src/common/thread.cxx:771
#6 0x00000000 in ?? ()
-- After patch: ----
gdb> bt
#0 do_some_random_computation (p=<optimized out>) at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/net/lwip_tcpip/current/tests/nc_test_slave.c:684
#1 net_load (who=<optimized out>) at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/net/lwip_tcpip/current/tests/nc_test_slave.c:668
#2 0x000033be in Cyg_HardwareThread::thread_entry (thread=0x1fff28d8)
at
/home/vae/Proekti/ecos/repo/cvs/current/ecos_kin/packages/kernel/current/src/common/thread.cxx:94
-------------------------------------------------------------------------------
> I would suggest something like:
>
> --with-pkgversion='eCos GNU tools 4.6.2-20120124'
Accepted and incorporated.
>
> I have suitably old Linux and Cygwin installations here and can generate
> releases based on your patches if you prefer.
I also did some fixes/clean up/branding to GCC and I'm doing the final
tests. I'll take Sergei's suggestion for using Bugzilla obsoleting
feature as VCS, so later evening or during the weekend I am going to put
all patches and scripts in a private maintainer bug - for review as well
as for you to pick them up for building.
Ilija
prev parent reply other threads:[~2012-01-27 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 18:03 Ilija Kocho
2012-01-24 21:45 ` John Dallaway
2012-01-24 23:40 ` Ilija Kocho
2012-01-25 6:42 ` Sergei Gavrikov
2012-01-27 14:32 ` Ilija Kocho [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F22B567.4070403@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).