Add new "nrelay" debug channel - useful for debugging GPFs in target applications
bon at elektron.ikp.physik.tu-darmstadt.de
Wed Mar 2 03:20:45 CST 2005
>>>>> "Andreas" == Andreas Mohr <andi at rhlx01.fht-esslingen.de> writes:
Andreas> Hi, On Wed, Mar 02, 2005 at 04:09:36PM +1100, Troy Rollo wrote:
>> The nrelay ("native relay") debug channel acts to limit the output of
>> the relay debug channel, and only works if the relay debug channel is
>> also on. When "nrelay" is on, "relay" will not log calls made from
>> one built-in library to another built-in library, or within a
>> built-in library. Thus each call logged is a call made directly by
>> the target application or by one of the native DLLs it depends on.
Andreas> Yay!! Thanks a lot! This one is VERY important, since
Andreas> developer confusion by overwhelmingly big and mostly less
Andreas> useful relay logs in recent years has grown a lot, I'd say.
Andreas> One suggestion: maybe make *only* logging external relays the
Andreas> default, and add a wrelay channel to add back the logging of
Andreas> Wine inter-dll calls? This might make more sense even, since
Andreas> you're often not interested at all in Wine interactions, but
Andreas> what the target app does.
Andreas> Any suggestions about the average percentage where people are
Andreas> interested in app-only calls as opposed to a full relay log?
Andreas> That would then tell us which way to implement this limiting.
Andreas> I'm not sure about the percentage, since I haven't done much
Andreas> development in recent years.
I also suggest to make the behaviour described by Andi the
default. Otherwise a very good feature. Thanks!
Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the wine-devel