Package: gdb-multiarch
Version: 7.4.1-3
Severity: normal

Dear Maintainer,

I just tried to debug a 64-bit program on my 32-bit system, and this is
what happened:

,----
| naesten@hydrogen:~/hacking/bugs% gdb-multiarch ./a.out
| GNU gdb (GDB) 7.4.1-debian
| Copyright (C) 2012 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 "i486-linux-gnu".
| For bug reporting instructions, please see:
| <http://www.gnu.org/software/gdb/bugs/>...
| "/home/naesten/hacking/bugs/a.out": not in executable format: File format not 
recognized
| (gdb) quit
| naesten@hydrogen:~/hacking/bugs% file a.out
| a.out: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked (uses shared libs), for GNU/Linux 2.6.26, 
BuildID[sha1]=0xf6dc19e094b96d7be361dfb0c2052f60857906aa, not stripped
`----

It seems that --enable-targets=all won't enable any 64-bit targets
on a 32-bit host without --enable-64-bit-bfd also being passed.

-- System Information:
Debian Release: 7.0
  APT prefers testing-proposed-updates
  APT policy: (991, 'testing-proposed-updates'), (990, 'testing'), (500, 
'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gdb-multiarch depends on:
ii  gdb           7.4.1-3
ii  libc6         2.13-37
ii  libexpat1     2.1.0-1
ii  libncurses5   5.9-10
ii  libpython2.7  2.7.3-6
ii  libreadline6  6.2-8
ii  libtinfo5     5.9-10
ii  zlib1g        1:1.2.7.dfsg-13

gdb-multiarch recommends no packages.

gdb-multiarch suggests no packages.

-- no debconf information

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to