On Wed, 24 Nov 2004 17:56:15 -0500, Coders Robert Story
<[EMAIL PROTECTED]> wrote:
> On Wed, 24 Nov 2004 10:00:50 +0100 P wrote:
> PK> 2) I got some sigsev's after deleting table row. I've changed
>
> How are you deleting the table row?
in _commit function I call some system functions to remove data from
system (in this case I call system("isdnctrl blah blah blah") to
remove isdn interface). I don't touch cache or so, but I had turned
OFF ,,dont updata caceh on set'' option (flag in _interface.c file).
>
> <tap tap tap>
>
> Hmm, ok, I'm remembering a similar problem that happened with undo.
>
> I'd really like to see a stack trace for the crash without this fix, as nobody
> should be referencing the row request context after it has been deleted! One
> of
> the memory debuggers (efence, dmalloc) might help track this down pretty fast,
> too.
Right. But it's embdeded system based on power-pc and there is no
,,dmalloc out of the box''. Maybe I will build one....
> Hmm... I'll have to think about it, but that sounds like a good idea...
:) And one more: add column_skip_flag to rowreq_ctx. Cache_load can
set some bits to '1' that mean that there is no values in some column.
Then _get can return MFD_SKIP for that column.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
