|
From: gwen r. <gwe...@bt...> - 2008-09-05 06:50:47
|
A piece of software I'm working on has a compatibility problem when running Valgrind.. Since I'm quite unfamiliar with the code I'm testing it'd be easier for me to change Valgrind to use a different signal number - possible? Cheers
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
|
|
From: Julian S. <js...@ac...> - 2008-09-05 07:18:12
|
On Friday 05 September 2008, gwen robson wrote: > A piece of software I'm working on has a compatibility problem when running > Valgrind.. Since I'm quite unfamiliar with the code I'm testing it'd be > easier for me to change Valgrind to use a different signal number - > possible? I vaguely remember some nasty hacks to do with threads and signals in very old valgrinds, but I thought they had mostly gone away by now. What version are you using? J |
|
From: Tom H. <to...@co...> - 2008-09-05 08:23:58
|
Julian Seward wrote: > On Friday 05 September 2008, gwen robson wrote: >> A piece of software I'm working on has a compatibility problem when running >> Valgrind.. Since I'm quite unfamiliar with the code I'm testing it'd be >> easier for me to change Valgrind to use a different signal number - >> possible? > > I vaguely remember some nasty hacks to do with threads and signals in > very old valgrinds, but I thought they had mostly gone away by now. > What version are you using? We still do it - we reserve the top signal (RT31) for VG_SIGVGKILL which is used for signalling the internal execution threads to when we want to make them run and they may be blocked in a system call. The number could be changed in pub_core_signals.h but the logic used to protect the signal from user changes would have to be changed as we currently assume the reserved signals are at the top of the signal number range and just protect any signal above VG_SIGVGRTUSERMAX from being altered. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |