More often than not, a core dump results from a pointer being 'stepped on'. Either you have used more space
than you allocated for an array (or pointer to a block of memory), or you have neglected to allocate it. If
the text is showing up in the multiline input, then backtrack from there to all your pointers. If it is not
showing up in your multiline input, then you have a leak elsewhere, and you need to find where your code is
going when you are typing. If you do not have a good debugger, well-placed output statements will get you in
the right area. But you first must know where _in_the_code_ your program is bombing off. The visual clues
from any gui can be very misleading. The problem may have occurred elsewhere, and is being aggravated by
your input box.
Duane Penzien wrote:
> # To subscribers of the xforms list from Duane Penzien <duano@bignet.net> :
>
> I posted this reply on the 3rd of July, apparently it did not make it thru. Hope it makes it this time:)
>
> I see that others have tried this using similar, but not the same, linux
> setup and it does not crash for you. Bear with me a little longer, I
> need to ask just one other question before I consider upgrading my linux
> version, libc library, x server, or whatever.
>
> When I cause the core dump to occur, it happens after repeating the
> following sequence of actions with the crn form already on display:
> 1) Select the Add/Edit memo object.
> 2) Type in some text *without* clicking on the multiline input
> object with the mouse first.
> 3) Click on the "Accept" button object to return to the crn form.
> 4) Repeat 1-3 until it core dumps (usually 10-15 times for me with
> this test program).
>
> If you have done this and cannot make it core dump, what would you
> suggest I try upgrading on this system first to get rid of the problem
> that I am having?
>
> Many thanks for the help!
>
> Duane Penzien wrote:
>
> > I am having a problem with a multiline_input object that core dumps when
> >
> > the memo form is displayed and the input object is in 'focus', but not
> > actually clicked on with the mouse. Attached to this message is a
> > file t2.c, which illustrates this problem when compiled. In the actual
> > program, this problem occurs usually when the memo form is called the
> > first, second, or third time. In the test program, it usually happens
> > around when memo form is called 8-10 times. Anyone got a fix for this?
> >
> > libc v2.7.2
> > xforms 0.88.1
> > xfree v 3.1.12
> > linux kernel 2.0.29 (i-486)
> >
> > --
> > <snip> <snip>
>
> --
> > A message from Duane Penzien, D.Penzien@computer.org <
> > Engineer, Writer, Gardener, Linux enthusiast <
>
> _________________________________________________
> To unsubscribe, send the message "unsubscribe" to
> xforms-request@bob.usuf2.usuhs.mil or see
> http://bob.usuf2.usuhs.mil/mailserv/xforms.html
> XForms Home Page: http://bragg.phys.uwm.edu/xforms
> List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/