From: Vincent Pelletier <subdino2004@yahoo.fr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: backtrace support
Date: Tue, 23 Aug 2005 09:46:39 +0200 [thread overview]
Message-ID: <430AD45F.4000605@yahoo.fr> (raw)
In-Reply-To: <430A4263.1020103@inma.ucl.ac.be>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vincent Guffens wrote:
> This is a problem because I would say that it breaks compilation for
> other architectures. I think that the other architectures should have a
> function grub_backtrace() that does nothing, or even better that really
> does print a backtrace(). However, I don't know how to do it and I can't
> test it anyway.
For sparc64-ieee1275, there is a ctrace command in open firmware which
does that work. grub_backtrace() could do a
grub_ieee1275_interpret("ctrace",NULL);
then
grub_ieee1275_exit();
To make ctrace work the ELF has to be unstripped - for now I hardcoded
it in conf/sparc64-ieee1275.rmk. To my experience, -O1 produces an
easier to understand ASM than -O0 (sparc64-ieee1275 allows to run in
step-by-step or breakpoint mode) because -O0 does really dumb things
that is very verbose in ASM line number. But I don't know in details
what -O1 does, and if it has drawbacks in optimisation (I think about
local functions).
> I hope this backtrace will be usefull, but not too much !
I have already found a use for it : I can't make vbetest work, it fails
with out of range pointer.
I hope it will be committed soon.
Oh, by the way, I'm trying to implement the OpenFirmware framebuffer
primitives - for now with no luck - so we can have it on ieee1275 ports.
There are lots of FCODE examples on Google, but all for PPC.
My current problem is how to allocate memory for the framebuffer itself,
and how to pass the address "to frame_buffer_adr" (the usual FCODE way
to store a value), if possible without using grub_ieee1275_interpret.
Vincent Pelletier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDCtRfFEQoKRQyjtURArwAAJ0QJ9cOK7WTW40UKVdf5O12vU9x5ACfcmXC
wmVVj2BJem/7hlyZ4boBMp8=
=lCgj
-----END PGP SIGNATURE-----
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2005-08-23 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:23 backtrace support Vincent Guffens
2005-08-23 7:46 ` Vincent Pelletier [this message]
2005-08-28 12:49 ` Yoshinori K. Okuji
2005-08-29 9:47 ` Vincent Guffens
2005-08-28 13:47 ` Marco Gerards
2005-08-29 11:20 ` Vincent Guffens
2005-08-31 19:01 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 20:22 Vincent Guffens
2005-08-18 20:58 ` Marco Gerards
2005-08-18 21:19 ` Vincent Guffens
2005-08-19 1:01 ` Yoshinori K. Okuji
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=430AD45F.4000605@yahoo.fr \
--to=subdino2004@yahoo.fr \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.