RE: Unsupported relocation type

["Mao, Bibo" <bibo.mao@intel.com>]

IA64 elfutils tool needs one patch, it is word-wrapped because of my windows email client:(

Thanks
Bibo,mao
--- elfutils-0.120/backends/ia64_symbol.c       2006-04-04 18:17:37.000000000 -0400
+++ elfutils-0.120.bak/backends/ia64_symbol.c   2006-04-21 09:18:15.000000000 -0400
@@ -110,10 +110,12 @@ ia64_reloc_simple_type (Ebl *ebl, int ty
   switch (type)
     {
     case R_IA64_DIR32MSB:
+    case R_IA64_SECREL32MSB:
       if (ebl->data == ELFDATA2MSB)
        return ELF_T_WORD;
       break;
     case R_IA64_DIR32LSB:
+    case R_IA64_SECREL32LSB:
       if (ebl->data == ELFDATA2LSB)
        return ELF_T_WORD;
       break;

>-----Original Message-----
>From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org]
>On Behalf Of Alan David Brunelle
>Sent: 2006年6月9日 22:29
>To: systemtap@sourceware.org
>Subject: Unsupported relocation type
>
>I'm starting to utilize SystemTap (btw: this is _really_ cool stuff),
>anyhow, I've been able to run a script on an Opteron system (RHEL4 U3),
>but on an IA64 system (RHEL4 U3) I see the following error :
>
>[root@powis 06_09]# stap -vg scwrite.stp
>Pass 1: parsed user script and 10 library script(s) in 79usr/0sys/80real ms.
>semantic error: cannot find module scsi_mod debuginfo: Unsupported
>relocation type
>semantic error: no match for probe point
>         while: resolving probe point
>module("*scsi_mod*").function("scsi_dispatch_cmd")
>semantic error: cannot find module scsi_mod debuginfo: Unsupported
>relocation type
>semantic error: no match for probe point
>         while: resolving probe point
>module("*scsi_mod*").function("scsi_done")Pass 2: analyzed script: 2
>probe(s), 4 function(s), 7 global(s) in 2usr/1sys/4real ms.
>Pass 2: analysis failed.
>
>As noted, this runs fine on the Opteron box. stap -V returns:
>
>[root@powis 06_09]# stap -V
>SystemTap translator/driver (version 0.5.4 built 2006-02-02)
>Copyright (C) 2005-2006 Red Hat, Inc. and others
>This is free software; see the source for copying conditions.
>
>Googling around showed that a similar error was fixed by going to 0.5.4
>- is there something IA64-specific I should be looking at?
>
>Thanks,
>Alan