1831959 Members
3375 Online
110034 Solutions
New Discussion

Re: Help on RTC

 
Dhirendra Singh
Occasional Advisor

Help on RTC

Hi,
I am running RTC in Batch Mode to check memory leak.
In the middle i get the below error message from rtc

.rtcinit:13: Error in sourced command file:
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (__rtc_leaks_info) will be abandoned.

I do set the variable unwindonsignal to on in .gdbinit file but i still get the error message.
5 REPLIES 5
Dhirendra Singh
Occasional Advisor

Re: Help on RTC

Here is some messages from rtc...

DbConnection::connect > Connecting to: 'SPDAPP3/*****' ... Trying output file=/spdev1/fs_env/work/spdwrk3/dkumar/olcServer.19310.leaks
Trying output file=/spdev1/fs_env/work/spdwrk3/dkumar/olcServer.19310.heap
rtcinit is set height 0
set {int} &shlib_info_invalid=0
set {int} &__gdb_synchronizer=1
set heap-check frame-count 8
set heap-check min-leak-size 0
set heap-check min-heap-size 0
info threads
tb __sync_up_with_gdb
commands
silent
end
c
info leaks /spdev1/fs_env/work/spdwrk3/dkumar/olcServer.19310.leaks
info heap /spdev1/fs_env/work/spdwrk3/dkumar/olcServer.19310.heap
q
__rtc_check_leaks=1 __rtc_check_heap=1
gdb = /opt/langtools/bin/gdb
exec=/opt/langtools/bin/gdb pid=19310
pid is 19310
Exec file name is olcServer
forked successfully buf = /opt/langtools/bin/gdb cpid=0
execl(/opt/langtools/bin/gdb, /opt/langtools/bin/gdb, -p, 19310, -x, .rtcinit, -tty=/dev/null, -q, -brtc, -leaks, (char *)0)
* 1 system thread 703919 Priority:179 wait_for_gdb_here ()
at ../../../Src/gnu/gdb/infrtc.c:5549

Program received signal SIGSEGV, Segmentation fault
si_code: 1 - SEGV_MAPERR - Address not mapped to object.
OK
Customized GuidingApiProxy::guidingInit() succeeded
Dennis Handly
Acclaimed Contributor

Re: Help on RTC

Questions on complex wdb issue should be directed to: wdb-help@cup.hp.com

I assume you now have the released version of wdb 5.7?
I assume the application doesn't abort unless you do the batch checking?

Does "show heap-check" show scrambling on?
That could show up with signal 11.

Dhirendra Singh
Occasional Advisor

Re: Help on RTC

GDB version is 5.6.0 and this error comes only when i run RTC in batch mode.

Also scrambling is off.
below are the lines in the rtcconfig file

set heap-check off
set heap-check leaks on
set heap-check free off
set heap-check string off
set heap-check bounds off
set heap-check frame-count 20
set heap-check scramble off
utput_dir=/spdev1/fs_env/work/spdwrk3/dkumar
files=olcServer

Dennis Handly
Acclaimed Contributor

Re: Help on RTC

>GDB version is 5.6.0 and this error comes only when I run RTC in batch mode.

Please try the latest 5.7.
Also, even though it doesn't abort without the heap checking, any user corruption can move to a different place.

>Also scrambling is off.

You might want to turn that on, along with free, string, bounds and heap-check itself. You might want to reduce frame-count so it runs faster.
Mithun R N
Advisor

Re: Help on RTC

Hi Dhirendra,

Does your application use dlopen/shl_load calls to dynamically load in shared libraries ?

Please try the latest WDB 5.7 available at http://www.hp.com/go/wdb and do get back if you
face any more issues with it.

Thanks and regards,
Mithun