Opened 9 years ago

Closed 8 years ago

#8094 closed bug (fixed)

Long unknown source file makes Debugger window very wide

Reported by: bonefish Owned by: anevilyak
Priority: normal Milestone: R1
Component: Applications/Debugger Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86


hrev43130, gcc 2

When debugging a program and encountering a stack frame for which the source file path is available via debug info but which doesn't point to a file on disk (e.g. when cross-compiled) the string is shown above the source view. If the string is very long, the window is resized to accommodate it and the window can become very wide.

I think the path shouldn't affect the window size. It could be truncated (in the middle or at the start) and a tool tip could show the full path (possibly wrapped).

Change History (4)

comment:1 by anevilyak, 9 years ago

Owner: changed from bonefish to anevilyak
Status: newin-progress

comment:2 by anevilyak, 9 years ago

Partially resolved in hrev43207, the string is now truncated if it won't fit within the bounds. However, I'm a bit puzzled as to how to flag the view as not influencing the layout constraints. I tried giving it an explicit min and max size of B_SIZE_UNSET, but this only resulted in it completely preventing any size changes whatsoever to the window. How would one correctly flag such a view to not influence the layout calculations, and simply accept the width that results from the constraints calculated via all the other views?

comment:3 by bonefish, 9 years ago

Setting an explicit min size -- something like BSize(100, B_SIZE_UNSET) -- should do the trick. B_SIZE_UNSET for a dimension means that that dimension is not overridden. So this would force the view to have a minimum width of 100 (regardless of its contents), thus not influencing the window's min width any further.

comment:4 by anevilyak, 8 years ago

Resolution: fixed
Status: in-progressclosed

Completely forgot about this. Did so in hrev44086, seems to do the trick nicely. Thanks for the tip!

Note: See TracTickets for help on using tickets.