On Sun, 10 Aug 2008, Chris Young wrote:
I can make it crash in warn_user and get the backtrace :-)
It's too late by then -- you've gone past the point at which the failure
happened, so have lost the context. That said, it does confirm that the
issue's in the form submission code.
I could probably get more from gdb if I knew how to use it!
1: gdb ./NetSurf
2: breakpoint form_successful_controls
3: run
4: <Submit a form>
5: next
6: <repeat step 5 until something fails -- should be obvious. note the
failure point -- this will be the function call producing the result
that causes goto no_memory to happen>
7: breakpoint forms.c:<line number of the failure point>
8: run (answer yes to it asking you if you're sure)
9: <redo step 4>
10: step
11: <repeat steps 5-10 until you've found the problem>
J.
