Dear Reinhard, Le 03/11/2013 02:11, Reinhard Tartler a écrit : > Hi Thibaut, > > can you perhaps also provide a backtrace? It seems that there are no > public s390x porter machines where I could get that myself. > Unfortunately, I can't: gdb seems to be broken on s390x. Reporting bug as we speak: (sid_s390x-dchroot)thibaut@zelenka:~/buggy$ gdb --args yorick -i check.i GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "s390x-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib/yorick/bin/yorick...Reading symbols from /usr/lib/debug/usr/lib/yorick/bin/yorick...done. done. (gdb) r Starting program: /usr/bin/yorick -i check.i Couldn't write registers: Invalid argument. (gdb) > Also, I wonder why s390x would require -DPIC -fPIC in compilation > flags, but s390 would not. Where did you get that impression? As far as I can tell, the required flags are -fPIC -shared, on all platforms. In the meantime, I checked that my minimal example compiles and runs fine on wheezy s390x. I can't check sid s390 as it has been retired. Kind regards, Thibaut.
Attachment:
signature.asc
Description: OpenPGP digital signature