public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Korn <dkorn@pixelpower.com>
To: 'Jerry Miller' <gmiller@cs.sunysb.edu>, help-gcc@gnu.org
Subject: RE: remote XOpenDisplay in Solaris (SunOS 5.6)
Date: Wed, 28 Feb 2001 02:23:00 -0000	[thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A564270B@EXCHANGESERVER> (raw)

>-----Original Message-----
>From: Jerry Miller [ mailto:gmiller@cs.sunysb.edu ]
>Sent: 27 February 2001 19:17

>Here's a dump of the first few values in big-endian
>shortword format (patterned after od -x).  Does
>anyone know enough assembler for the UltraSparc 5
>(68XXX???) to be able to tell me where the address
>starts (and whether it is an actual address or a further
>indirection)?
>
>0300 099c 30bf fd98 0100 0000 0100 0000
>001f cb28 0000 0040 0000 0000 001f 802c
>
>A simple test program, which does nothing but call
>the dump function, instead yields:
>
>0300 0084 30bf ffde 0100 0000 0100 0000
>0002 0a88 0000 0000 0000 0000 0002 09b4

  Is this the actual linked code from memory, or are you dumping the 
object file here?  All those zeroes don't look right to me, so if this
is what's in memory, it looks like it hasn't been linked correctly.

>(Where's a disassembler when I need one?!?!)

  Right, let me think about this.  We know that the first few instructions
are the function prologue, so I'd reckon that those negative numbers
$fd98 and $ffde are the stack frame adjustments, so that would mean that
$30bf $xxxx is link #xxxx,a6.  $0a88 is one I vaguely recognize as well,
I think that's a load to a register....  All those zeroes just can't be
right though.

  I think your best bet is to run your program under gdb.  That will trap
on the segv and you can have a look at the stack frame and see which 
functions have been called by which other functions in which order.

       DaveK
-- 
 All your base are belong to us!


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

             reply	other threads:[~2001-02-28  2:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  2:23 David Korn [this message]
2001-02-28  6:20 ` Jerry Miller
  -- strict thread matches above, loose matches on Subject: below --
2001-02-28  7:24 David Korn
2001-02-28 10:47 ` Jerry Miller
2001-02-28  2:12 David Korn
2001-02-27 11:30 Jerry Miller
2001-02-27 11:19 Jerry Miller
2001-02-27 11:16 Jerry Miller
2001-02-23  9:57 David Korn
2001-02-23 10:50 ` Jerry Miller
2001-02-27 10:56   ` Jerry Miller
2001-02-23  8:39 David Korn
2001-02-23  9:41 ` Jerry Miller
2001-02-22 17:07 gcc compiler Salari, Morris M
2001-02-23  1:08 ` Jerry Miller
2001-02-23  8:28   ` remote XOpenDisplay in Solaris (SunOS 5.6) Jerry Miller

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=718D38CAB6E0D011B2C90060970C28A564270B@EXCHANGESERVER \
    --to=dkorn@pixelpower.com \
    --cc=gmiller@cs.sunysb.edu \
    --cc=help-gcc@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 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).