GDB error when breakpoint hit: no thread can be found to satisfy query

Question

Hi. I'm trying to track down leaks in a 32bit MT program on Solaris 10
sparc.
Without breakpoints the program works normally, but if I place
breakpoints to the suspicious places, when the program starts to
actively use threads, very soon gdb prints the following error and
can't continue:
[LWP    21         exited]
sol_thread_fetch_registers: td_ta_map_id2thr: no thread can be found to satisfy query
Currently I'm using gdb 7.1. I was getting a similar error with gdb
6.8 in the same conditions:
procfs: fetch_registers, get_gregs line 3768, /proc/08694/lwp/21: No such file or directory.
[LWP 21 exited]
The command file sets some breakpoints to periodically print the backtrace
Any hints?
handle SIGABRT nostop pass
handle SIGTERM nostop pass
start
set breakpoint pending on
# 0xfdd0de88
# 0xfdd0de88 in nlnvmal () from /export/home/testora/product/10.2.0/Db_1/lib32/libclntsh.so.10.1
b *nlnvmal + 4
commands
backtrace
continue 200
end
# 0xfd92f080
# 0xfd92f0c8 in sqlalc () from /export/home/testora/product/10.2.0/Db_1/lib32/libclntsh.so.10.1
b *sqlalc + 4 + 0x48
commands
backtrace
continue 200
end
# 0xfe03d6f4
# 0xfe03d7ec in kpummapg () from /export/home/testora/product/10.2.0/Db_1/lib32/libclntsh.so.10.1
b *kpummapg + 4 + 0xf8
commands
backtrace
continue 100
end
# continue
#

Answer 1

Hi Ram,
This error is almost always caused by incomplete or incorrect customizing:
In addition, the summarization level must have status 'ACTIVE' (this applies also to the search function in the maintenance transaction for CO-PA data sources,KEB0).                                                                               
Please also review the SAP note 392635 which is release independent and has further information on the customizing and CO-PA extraction:                                                                               
392635 - Information: Sources with BW extraction for account-based    
           CO-PA                                                        
So please check your customizing and the note 392635 carefully in particular please pay attention to the following:                                                                               
There has to be one (single)  summarization level that contains all characteristics (except for  the controlling area) with '*' in the   
characteristics view in  transaction KEDV and has status 'active'.   
After checking the above you need to replicate the datasource in the connected BW system and reactivate the transfer rules.               
Best Regards,
Des