From: Russell Browne (russ_at_amc.com)
Date: Thu Aug 03 2000 - 21:07:10 BST
I'd like some input from UPS users on the defaults provided for some recent UPS features. 1. Memory dump for little endian targets: The memory dump feature was added with release 3.34. If you dump memory for a structure or an object of type void*, or if you type %d 12345678, you get a display like this: Big endian: 12345678: 6061 6263 6465 6667 6869 6a6b 6c6d 6e6f @abcdefghijklmno Little endian: 12345678: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f @abcdefghijklmno My question is whether, in the little endian case, it would be better to group the data as longs by default, so that it would look like this: 12345678: 63626160 67666564 6b6a6968 6f6e6d6c @abcdefghijklmno The current byte display was selected on the grounds of doing as little intrepretation of the data as possible. But it seems to me that in most cases data consists of ints and/or pointers so that a four byte grouping would be best or the data is a string so that the ascii display is of interest and the grouping doesn't matter. Any feelings, one way or the other, on changing the default grouping to longs for little endian targets. 2. Lower main window on Start/Cont The recent beta versions of release 3.35 will, by default, lower the main UPS window 1.5 seconds after the target goes into run if it doesn't hit a breakpoint or otherwise stop first. You can turn this on or off interactively through the Windows menu, and can change the default behavior with an X resource or call line parameter. You can also change the 1.5 second delay with an X resource. Two questions on this: First, is lowering the main window the best default behavior? I usually like to see UPS get out of the way so that I can interact with the application I'm dubugging, which is why I made lowering the window the default. But I recently found a problem with this (on sun4) so irratating that I wondered if beta users are simply turning the feature off and so not reporting problems. (The problem, now corrected, was that once UPS lowered itself it refused to come back to the top; raising it with the window manager simply flashed it on the screen.) Any feelings on whether it would be better, as a default, to simply raise the main window when the target stops? Second, for those who like the lower on run feature, is 1.5 seconds a good delay? You want some delay so that UPS doesn't disappear and come back when you run to a nearby breakpoint. But 1.5 seconds is long enough that I find myself starting to lower the window, or raise the application window, manually before UPS does it for me. I've set the delay to .75 seconds in my .Xdefaults file, which works better for me. For those who want to experiment, the resource that does this is: Ups.LowerOnRunTime: 750 /* Time delay before lowering, in ms. */ Any feelings on the best delay before UPS lowers itself? Russ Browne Applied MicroSystems Corp.
This archive was generated by hypermail 2.1.4 : Wed Feb 13 2002 - 21:51:33 GMT