libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libunwind] _ReadSLEB and _ReadULEB


From: Tommy Hoffner
Subject: Re: [libunwind] _ReadSLEB and _ReadULEB
Date: Wed, 16 Feb 2005 09:46:34 +0100
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

David Mosberger skrev:
On Thu, 10 Feb 2005 12:50:46 +0100, Tommy Hoffner

<address@hidden> said:

  Tommy> Enclosing an example that fails for me. The first catch works
  Tommy> and the second loops, so swapping them makes the other one
  Tommy> fail.

Hmmh, I do:

 $ icpc -V
 Intel(R) C++ Itanium(R) Compiler for Itanium(R)-based applications
 Version 8.1    Build 20041021 Package ID: <installpackageid>
 $ make
 $ ./LEBbug
 SUCCESS! (Caught 7)

 $ ./LEBbug  a
 SUCCESS! (Caught Exception)

Looks OK to me.  Am I missing something?
Ok, that is also a result. I'll keep investigating.
Two thoughts though:
I use a newer icc:
"Intel(R) C Itanium(R) Compiler for Itanium(R)-based applications
Version 8.1    Build 20041123 Package ID: l_cc_pc_8.1.026
Copyright (C) 1985-2004 Intel Corporation.  All rights reserved."

I don't remember if that also means that libipr got updated (Intel release notes doesn't reveal info about the libraries and they don't contain any usable version numbers :-(. My libraries have the following checksums:

address@hidden:~/src/NIL$ sum --version
sum (coreutils) 5.2.1
address@hidden sum /opt/intel_cc_80/lib/libipr.*
07346    12 /opt/intel_cc_80/lib/libipr.a
00999     1 /opt/intel_cc_80/lib/libipr.so
32283    13 /opt/intel_cc_80/lib/libipr.so.6

Secondly, since name resolution in dynamic libraries isn't the most predictable activity that I know: Can you verify that your build/run results in Intel's personality routine calling your _ReadSLEB?

/Tommy


        --david


--
Tommy Hoffner
Senior Software Designer
Compiler Technology

Ericsson AB
Development Unit Core Network Evolution
Tel:    +46 13 23 57 12
Fax:    +46 13 28 73 71
SMS/MMS:+46 730 43 61 56
address@hidden
www.ericsson.com

This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete the
message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]