From: "Jafa" <jafa@silicondust.com>
To: <gdb@sources.redhat.com>
Subject: Frame handling
Date: Tue, 08 Apr 2003 18:35:00 -0000 [thread overview]
Message-ID: <00c801c2fdfd$68a82b40$f601a8c0@scenix.com> (raw)
Hi all,
I am working on the ip2k port of GDB. It has been stable for some time now
but I ran out of time to get it reviewed before I went on holiday and now I
am trying to bring it up to date with the trunk again.
I merged with the trunk on March 17 - big mistake... frame handling was
cauing big problems.... looked like a partical update to a new approach.
I have just checked out the trunk today and it looks like a number of the
ports are using the new frame handling approach.
Is the trunk considered ok ATM or is the frame handling still in unstable
daily development?
What port would you recommend for reference for frame handling? The MIPS
port is using deprecated frame functions.
BTW - The stack-backtraces have a second problem as well... GDB is ment to
stop at 'main' but the symbol lookup fails. In the applications that I am
testing the symbol 'main' is a weak alias and this seams to be a general
problem in the symbol lookup.
I would appreciate your advice.
Thanks
Nick
next reply other threads:[~2003-04-08 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 18:35 Jafa [this message]
2003-04-14 3:43 ` Andrew Cagney
2003-07-01 1:20 Jafa
2003-07-01 3:42 ` Daniel Jacobowitz
2003-07-01 4:18 ` Andrew Cagney
[not found] ` <redirect-6800274@silicondust.com>
2003-07-01 5:13 ` Jafa
2003-07-01 12:58 ` Andrew Cagney
2003-07-01 14:09 ` Daniel Jacobowitz
2003-07-01 14:57 ` Andrew Cagney
[not found] ` <redirect-6810110@silicondust.com>
2003-07-01 17:00 ` Jafa
[not found] ` <redirect-6810084@silicondust.com>
2003-07-01 16:14 ` Jafa
2003-07-01 17:59 ` Andrew Cagney
2003-07-01 5:00 Jafa
2003-07-01 12:45 ` Daniel Jacobowitz
2003-07-01 13:02 ` Andrew Cagney
2003-07-03 9:05 ` Paul N. Hilfinger
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='00c801c2fdfd$68a82b40$f601a8c0@scenix.com' \
--to=jafa@silicondust.com \
--cc=gdb@sources.redhat.com \
/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