Re: Segmentation fault

2009/7/6 Mike Ayers <[email protected]>:
>        I notice that you are stting each variable twice in succession

Actually, the code seems to be issuing a SET followed by a GET
(presumably to check whether the assignment worked).
  This shouldn't cause any problems.

I'm not familiar with the python interface, so I can't comment on
what the underlying problem might be.   You may need to try and
pin down the exact characteristics that trigger the problem.
  Is it a particular type of assignment, or a particular value?  Does
the order in which assignments are applied make a difference?
Is it the same behaviour every time, or is there some element of
randomness?

  (I'm presuming that this *is* python code - it looks like it to my
   untutored eye, but you never actually say).


> ... the use of createAndGo in this fashion will never work (unless,
> of course, the MIB implementation is severely broken).

I could quibble, and point out that an individual createAndGo assigment
would work if there were (implicit or explicit) default values for every
column object in the table.
   But I would agree that it doesn't really make sense in this particular
script, since all of the previous assignments would have failed anyway
if the row didn't already exist.

Dave

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have 
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users