From: Alex LIU <alex.liu@st.com>
To: UML-dev <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Question about UML gdb
Date: Wed, 27 Apr 2005 17:04:34 +0800 [thread overview]
Message-ID: <002901c54b08$223494a0$90b3c68a@SHZ.ST.COM> (raw)
Hi all:
I have 2 questions about UML gdb:
1.how to get the address of current process UML gdb?
It seems "esp & 0xffffe000" is not the correct address.
2.how to read the contents of a file in UML gdb?
The file is an object of struct file. I only know the address of the file.
Thanks a lot!
Alex
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2005-04-27 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 9:04 Alex LIU [this message]
2005-04-27 21:50 ` [uml-devel] Question about UML gdb stian
2005-04-28 11:29 ` Nix
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='002901c54b08$223494a0$90b3c68a@SHZ.ST.COM' \
--to=alex.liu@st.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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