Debian Bug report logs - #799556
GDB cannot debug a program on the X32 platform (internal-error: find_new_threads_once...)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jeffrey Walton <noloader@gmail.com>

To: submit@bugs.debian.org

Subject: GDB cannot debug a program on the X32 platform (internal-error: find_new_threads_once...)

Date: Sun, 20 Sep 2015 06:05:40 -0400

Package: gdb
Version: 7-10.1
Severity: important
X-Debbugs-CC: zumbi@debian.org, gcs@debian.org

*****

A Debian maintainer informed us of some problem on the X32 platform.
I'm attempting to perform the port to X32, but I can't seem to get GDB
to execute/debug a program on the X32 platform (see below).

Info on the X32 platform can be found at https://wiki.debian.org/X32Port.

*****

Here is the problem I am experiencing.

# gdb cryptest.exe
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 "x86_64-linux-gnux32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cryptest.exe...done.
(gdb) r v
Starting program: /home/cryptopp-5.6.3/cryptest.exe v
warning: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER: Input/output error
/build/gdb-gaG2aU/gdb-7.10/gdb/linux-thread-db.c:1675: internal-error:
find_new_threads_once: Assertion `!target_has_execution ||
thread_db_use_events ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

*****

# apt-cache show gdb
Package: gdb
Priority: optional
Section: devel
Installed-Size: 6419
Maintainer: Héctor Orón Martínez <zumbi@debian.org>
Architecture: x32
Version: 7.10-1
Replaces: gdb
Depends: libc6 (>= 2.16), libexpat1 (>= 2.0.1), liblzma5 (>=
5.1.1alpha+20110809), libncurses5 (>= 6), libpython3.4 (>= 3.4.2),
libreadline6 (>= 6.0), libtinfo5 (>= 6), zlib1g (>= 1:1.2.0)
Recommends: libc-dbg, gdbserver
Suggests: gdb-doc
Conflicts: gdb
Filename: pool-x32/main/g/gdb/gdb_7.10-1_x32.deb
Size: 2398182
MD5Sum: 53d794fd2bfb5b4b1cfc88c2601d0063
SHA1: d6063dadcd8548b735c82734fe354b425d7c3781
SHA256: 643e29f266a396d39d6ef91d0f72a6eeb7f3478577274ce22d10403fd702bdc7
SHA512: ab8429c16c7f7c8824306b8e55dfc2f674ff2071213210ee41e316e50497ba8efe7425d5c1bad7a3c53255d0c01a9bbbf95c415b7dd6917c70682ea53ae3097b
Description: GNU Debugger
 GDB is a source-level debugger, capable of breaking programs at
 any specific line, displaying variable values, and determining
 where errors occurred. Currently, gdb supports C, C++, D,
 Objective-C, Fortran, Java, OpenCL C, Pascal, assembly, Modula-2,
 Go, and Ada. A must-have for any serious programmer.
Description-md5: 4f2b8eb95df2ba7a5b11e0301c48b8e4
Homepage: http://www.gnu.org/s/gdb/

Message #10 received at 799556@bugs.debian.org (full text, mbox, reply):

From: Jeffrey Walton <noloader@gmail.com>

To: 799556@bugs.debian.org

Subject: Warning possibly contributing to the error in 799556

Date: Sun, 20 Sep 2015 17:31:21 -0400

Building GDB 7.10 from sources reveals:

  # export CFLAGS="-mx32"
  # export CXXFLAGS="-mx32"
  # ./configure --prefix=/usr/local
  checking build system type... x86_64-unknown-linux-gnu
  checking host system type... x86_64-unknown-linux-gnu
  checking target system type... x86_64-unknown-linux-gnu
  checking for a BSD-compatible install... /usr/bin/install -c
  ...

  # make

gcc -c -DHAVE_CONFIG_H -mx32  -I. -I./../include  -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic
-D_GNU_SOURCE ./getruntime.c -o getruntime.o
./getruntime.c: In function ‘get_run_time’:
./getruntime.c:98:14: warning: enum conversion when passing argument 1
of ‘getrusage’ is invalid in C++ [-Wc++-compat]
   getrusage (0, &rusage);
              ^
In file included from ./getruntime.c:47:0:
/usr/include/x86_64-linux-gnux32/sys/resource.h:87:12: note: expected
‘__rusage_who_t {aka enum __rusage_who}’ but argument is of type ‘int’
 extern int getrusage (__rusage_who_t __who, struct rusage *__usage) __THROW;
            ^

Message #15 received at 799556@bugs.debian.org (full text, mbox, reply):

From: Jeffrey Walton <noloader@gmail.com>

To: 799556@bugs.debian.org

Subject: Unwanted assert causing failure

Date: Sun, 20 Sep 2015 18:19:12 -0400

There's an unwanted assert causing the failure in
gdb/linux-thread-db.c. Around line 1675, guard the assert based on
__ILP32__:

#if !defined(__ILP32__) && !defined(_ILP32)
  /* See comment in thread_db_update_thread_list.  */
  gdb_assert (!target_has_execution || thread_db_use_events ());
#endif

Once the assert is removed for the X32 platform, the program can be
executed under GDB.

Message #20 received at 799556@bugs.debian.org (full text, mbox, reply):

From: Jeffrey Walton <noloader@gmail.com>

To: 799556@bugs.debian.org

Subject: Upstream GDB bug report with suggested fix

Date: Sun, 20 Sep 2015 18:43:28 -0400

See GDB Issue 18987, https://sourceware.org/bugzilla/show_bug.cgi?id=18987

Message #25 received at 799556@bugs.debian.org (full text, mbox, reply):

From: Jeffrey Walton <noloader@gmail.com>

To: 799556@bugs.debian.org

Subject: Control updates

Date: Mon, 21 Sep 2015 18:41:58 -0400

Control: user debian-x32@lists.debian.org
Control: usertags -1 + port-x32
Control: tags -1 + patch upstream

Message #48 received at 799556-done@bugs.debian.org (full text, mbox, reply):

From: Hector Oron <zumbi@debian.org>

To: 799556-done@bugs.debian.org, 827862-done@bugs.debian.org

Subject: Re: Bug#799556: Control updates

Date: Tue, 13 Dec 2016 00:13:47 +0100

[Message part 1 (text/plain, inline)]

Hello,

Resolving this issue as it is fixed now.

Regards,
-- 
  Hector Oron

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.