Previously...
On Tue, 11 Jan 2000, Dan Espen wrote:
>"Thomas A. Gardiner" <gardiner_at_pas.rochester.edu> writes:
>> Hi,
>>
>> I'm getting a segmentation fault from FvwmForm which only occurs when the
>> number of items grows to become comparable to the MAX_ITEMS definition in
>> FvwmForm.c.
>>
>> In fact changing this
>>
>> /* tba: use dynamic buffer expanding */
>> #define MAX_LINES 16
>> #define MAX_ITEMS 64
>>
>> to this
>>
>> /* tba: use dynamic buffer expanding */
>> #define MAX_LINES 26
>> #define MAX_ITEMS 84
>>
>> gets rid of the problem. So, the problem must be occuring in the dynamic
>> memory allocation. (This idea is born out from using gdb.)
>> Is anyone familiar enough with this code to be able to
>> track down this bug without having to learn it in it's entirety (sp?) like
>> I would? If not, I will try to take a stab at it.
>>
>> Tom
>>
>> Oh yeah... This occurs with both fvwm2.2.2 and fvwm2.2.4 .
>
>In the 2.3.x series, all of the limits in FvwmForm are removed.
So then do you, Dan, suggest that I simply use my down and dirty hack for
now and wait for the 2.3.x series since the memory managment issue is
apparently managed in a different way?
Tom
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Jan 11 2000 - 11:22:20 GMT