Bug 442765

Executing new program: /usr/lib/rpm/rpmk
Missing separate debuginfos, use: debuginfo-install elfutils.x86_64 gcc.x86_64
popt.x86_64
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
[New process 8704]
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdacacd4780 (LWP 8686)]
0x000000000046664e in thread_get_info_callback (thp=0x7fffd2cf8690,
infop=0x7fffd2cf86a8) at /usr/include/bits/string3.h:52
warning: Source file is more recent than executable.
52	  return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
Missing separate debuginfos, use: debuginfo-install elfutils.x86_64 gcc.x86_64
popt.x86_64 readline.x86_64
(gdb) bt
#0  0x000000000046664e in thread_get_info_callback (thp=0x7fffd2cf8690,
infop=0x7fffd2cf86a8) at /usr/include/bits/string3.h:52
#1  0x00000000004668ab in thread_from_lwp (ptid={pid = 8704, lwp = 8704, tid =
0}) at ../../gdb/linux-thread-db.c:351
#2  0x0000000000466c9d in thread_db_wait (ptid={pid = 8704, lwp = 8704, tid =
0}, ourstatus=0x7fffd2cf8780) at ../../gdb/linux-thread-db.c:889
#3  0x00000000004e1e09 in wait_for_inferior (treat_exec_as_sigtrap=0) at
../../gdb/infrun.c:1042
#4  0x00000000004e2127 in proceed (addr=<value optimized out>,
siggnal=TARGET_SIGNAL_0, step=0) at ../../gdb/infrun.c:854
#5  0x00000000004dc1ae in run_command_1 (args=0x0, from_tty=1,
tbreak_at_main=<value optimized out>) at ../../gdb/infcmd.c:563
#6  0x000000000044677a in execute_command (p=0x114ca43 "", from_tty=1) at
../../gdb/top.c:449
#7  0x00000000004ed74b in command_handler (command=0x114ca40 "") at
../../gdb/event-top.c:523
#8  0x00000000004ee62c in command_line_handler (rl=<value optimized out>) at
../../gdb/event-top.c:809
#9  0x0000003062027e7e in rl_callback_read_char () from /lib64/libreadline.so.5
#10 0x00000000004eda69 in rl_callback_read_char_wrapper (client_data=0x0) at
../../gdb/event-top.c:178
#11 0x00000000004ec37d in process_event () at ../../gdb/event-loop.c:341
#12 0x00000000004ecd36 in gdb_do_one_event (data=<value optimized out>) at
../../gdb/event-loop.c:378
#13 0x00000000004e9884 in catch_errors (func=0x4ecb30 <gdb_do_one_event>,
func_args=0x0, errstring=0x647c6a "", mask=<value optimized out>) at
../../gdb/exceptions.c:513
#14 0x0000000000491468 in tui_command_loop (data=<value optimized out>) at
../../gdb/tui/tui-interp.c:156
#15 0x000000000043e5b9 in captured_command_loop (data=0x0) at ../../gdb/main.c:99
#16 0x00000000004e9884 in catch_errors (func=0x43e5b0 <captured_command_loop>,
func_args=0x0, errstring=0x647c6a "", mask=<value optimized out>)
    at ../../gdb/exceptions.c:513
#17 0x000000000043f0b6 in captured_main (data=<value optimized out>) at
../../gdb/main.c:884
#18 0x00000000004e9884 in catch_errors (func=0x43e5f0 <captured_main>,
func_args=0x7fffd2cf8ea0, errstring=0x647c6a "", mask=<value optimized out>)
    at ../../gdb/exceptions.c:513
#19 0x000000000043e5a4 in gdb_main (args=0x7fffd2cf84a0) at ../../gdb/main.c:893
#20 0x000000000043e576 in main (argc=<value optimized out>, argv=0x7fffd2cf84a0)
at ../../gdb/gdb.c:33
(gdb) 

I have a backport available but still not committed due to failing
regression-tests for the new release in RHTS (Job 20573, Job 20605) and even
standalone but these problems are unrelated to this Bug.

It never worked before, the problem is trying to debug through the exec syscall
and together with threads, you may run /usr/lib/rpm/rpmk on its own instead as a
workaround.  F9 blocker is OK as it is just a backport.

* Wed Apr 16 2008 Jan Kratochvil <jan.kratochvil> - 6.8-4
- Backport fix on various forms of threads tracking across exec() (BZ 442765).

http://sourceware.org/ml/gdb-patches/2008-03/msg00281.html
http://sourceware.org/ml/gdb-cvs/2008-03/msg00114.html

Moving to target, this is not a release blocker.

gdb-6.8-5.fc9 has been submitted as an update for Fedora 9

gdb-6.8-5.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.