Navigation
RSS Feeds
Unaligned access problem in Suse10-64-bit (HP-ia64 architecture)
Posted by krishnan_tom
on 2008-02-27 22:13
OS: Suse / OpenSuse
hi ,
I am trying to port the activetcl8.4 (which was installed on 32-bit SuseOS ) onto to HP-ia64. I used the source code provided with the tcldevkit. When i am trying to run my application on this ActiveTcl , it is giving the following warning:
"wish(2646): unaligned access to 0x600000000059863c, ip=0x2000000000d310f0"
It seems like a memory access problem.
How can avoid this warning?
Thanks
- Login to post comments
Can you elaborate a bit more on exactly what build of ActiveTcl you are using, and on what OS/Platform you are trying to run it on? uname -a for the latter, and 'parray tcl_platform ; parray activestate::config' for the former please.
1: Installed Tcl on 32-bit SuseOS
2: Copied the installation to HP-ia64. Uname of this m/c:
linux-hp-4:/opt/SEK/bin # Linux linux-hp-4 2.6.16.46-0.12-default #1 SMP Thu May 17 14:00:09 UTC 2007 ia64 ia64 ia64 GNU/Linux
3: Replaced the libraries:
a. copy source (.o files) from tcldevkit into the HP-ia64
b. run '.configure' and 'make'
c. replace the newly built .so files into tcl folder (copied in step 2 above)
4: Prepare our product for HP-ia64
a. Compile our source using Tcldevkit copiler on Windowx XP 32 bit
b. copy the compiled files to HP-ia64
5: Run our source on HP-ia64
When this is run the messages given are:
wish(13975): unaligned access to 0x600000000034d40c, ip=0x2000000000dd50d0
wish(13975): unaligned access to 0x600000000034d414, ip=0x2000000000dd50d1
wish(13975): unaligned access to 0x600000000034d41c, ip=0x2000000000dd50e0
wish(13975): unaligned access to 0x600000000034d424, ip=0x2000000000dd50e1
wish(13975): unaligned access to 0x600000000034d42c, ip=0x2000000000dd50f0
Even after this our product launches and works fine.
We have not done complete testing to verify all functionalities
We also found that the messages were generated due to the following code:
set licDom [dom parse -keepEmpties $m_strLicContent]
Can you let us know if these messages must be looked into and what is the solution.
This problem has been standing for some time now and it is important that we solve it immediately.
Thanks
What is step 3 about? There shouldn't be anything in the TDK that you need to recompile.
As for [dom parse] causing the problem, it has its own built-in memory allocator for extra performance. This may have some issues that don't directly translate in the special x86-on-ia64 translation mode you have.
Thanks Jeff,
Actually in step 3 ,i have mentioned about the tbcload source code which comes with the TCLDevKit.