On Mon, May 21, 2018 at 02:36:43PM -0400, Bill Fenner wrote:
> On Mon, May 21, 2018 at 11:18 AM, Wes Hardaker <
> [email protected]> wrote:
>
> > Bill Fenner writes:
> >
> > > So, +1 on committing Bart's patch, because it accomplishes the goal of
> > > fixing the regression, with the
On Mon, May 21, 2018 at 11:18 AM, Wes Hardaker <
[email protected]> wrote:
> Bill Fenner writes:
>
> > So, +1 on committing Bart's patch, because it accomplishes the goal of
> > fixing the regression, with the caveat that I really think that this
> > whole area needs to be revisited.
Bill Fenner writes:
> So, +1 on committing Bart's patch, because it accomplishes the goal of
> fixing the regression, with the caveat that I really think that this
> whole area needs to be revisited.
I think this comment is spot on. So I'd accept the patch too, though my
gut reaction is to reve
On Sun, May 20, 2018 at 2:25 PM, Robert Story wrote:
> On Sun, 20 May 2018 13:06:43 -0400 Bill wrote:
> BF> I do not think that now is the time to try to deal with any of
> BF> the fundamentals, but just not regress from previous released
> BF> behavior, and deal with the underlying issue in 5.8.
On Sun, 20 May 2018 13:06:43 -0400 Bill wrote:
BF> I do not think that now is the time to try to deal with any of
BF> the fundamentals, but just not regress from previous released
BF> behavior, and deal with the underlying issue in 5.8.1 / 5.7.4.
Just to clarify, do you mean
a) accepts Bart's RF
On Sun, May 20, 2018 at 12:18 AM, Robert Story wrote:
> On Sat, 19 May 2018 14:07:56 -0700 Bart wrote:
> BVA> strlcpy() implementations typically scan for the end of the
> BVA> source argument passed to strlcpy(). Hence avoid passing an
> BVA> unterminated string to strlcpy().
>
> I'm going to sa
On 05/19/18 21:18, Robert Story wrote:
On Sat, 19 May 2018 14:07:56 -0700 Bart wrote:
BVA> strlcpy() implementations typically scan for the end of the
BVA> source argument passed to strlcpy(). Hence avoid passing an
BVA> unterminated string to strlcpy().
I'm going to say -1, but for the patch an
On Sat, May 19, 2018 at 05:28:31PM -0700, Bart Van Assche wrote:
> On 05/19/18 15:14, Magnus Fromreide wrote:
> > On Sat, May 19, 2018 at 02:07:56PM -0700, Bart Van Assche wrote:
> > > strlcpy() implementations typically scan for the end of the source
> > > argument
> > > passed to strlcpy(). Henc
On Sat, 19 May 2018 14:07:56 -0700 Bart wrote:
BVA> strlcpy() implementations typically scan for the end of the
BVA> source argument passed to strlcpy(). Hence avoid passing an
BVA> unterminated string to strlcpy().
I'm going to say -1, but for the patch and not the need to fix the
issue.
This co
On 05/19/18 15:14, Magnus Fromreide wrote:
On Sat, May 19, 2018 at 02:07:56PM -0700, Bart Van Assche wrote:
strlcpy() implementations typically scan for the end of the source argument
passed to strlcpy(). Hence avoid passing an unterminated string to strlcpy().
Reported-by: Stuart Henderson
Fi
On Sat, May 19, 2018 at 02:07:56PM -0700, Bart Van Assche wrote:
> strlcpy() implementations typically scan for the end of the source argument
> passed to strlcpy(). Hence avoid passing an unterminated string to strlcpy().
>
> Reported-by: Stuart Henderson
> Fixes: 7f05daa8e0e0 ("CHANGES: BUG: 34
On 2018/05/19 14:07, Bart Van Assche wrote:
> strlcpy() implementations typically scan for the end of the source argument
> passed to strlcpy(). Hence avoid passing an unterminated string to strlcpy().
>
> Reported-by: Stuart Henderson
> Fixes: 7f05daa8e0e0 ("CHANGES: BUG: 3444939: BUG: 1796886:
strlcpy() implementations typically scan for the end of the source argument
passed to strlcpy(). Hence avoid passing an unterminated string to strlcpy().
Reported-by: Stuart Henderson
Fixes: 7f05daa8e0e0 ("CHANGES: BUG: 3444939: BUG: 1796886: snmplib: Avoid that
sprint_realloc_octet_string() emb
On Fri, Jan 21, 2011 at 01:48:47PM +0300, Egor wrote:
> I wrote my own simple MIB module, used mib2c.scalar.conf. So, I made my
> example like delayed_instance.c.
> this is received by gdb:
> Program received signal SIGSEGV, Segmentation fault.
> _int_malloc (av=, bytes=) at
netsnmp_set_request_error(reqinfo, requests,
SNMP_ERR_UNDOFAILED);
}
DEBUGMSGTL(("simpleMib", "mode_set_undo_ok\n"));
break;
default:
/* we should never get here, so this is a really bad error */
snm
When I restarting my subagent I got this
Program received signal SIGSEGV, Segmentation fault.
0x76681765 in netsnmp_oid_find_prefix () from
/usr/lib64/libnetsnmp.so.15
What might be the cause?
Regards,
Prakash Raju
logo
A leader in technology driven business solutions
>Hi All
>
>I need your help to fix the following issue for Solaris box:
>$ /usr/local/sbin/snmpd -f -Le
>Segmentation Fault
>$
># /usr/local/sbin/snmpd -f -Le
>Segmentation Fault (core dumped)
>#
Can you read the following web page and hopefully it'll h
Hi All
I need your help to fix the following issue for Solaris box:
$ /usr/local/sbin/snmpd -f -Le
Segmentation Fault
$
# /usr/local/sbin/snmpd -f -Le
Segmentation Fault (core dumped)
#
--
GAURAV SHARMA
--
ThinkGeek
On 15 March 2010 10:27, Manjit wrote:
> For some of the value(wrong values ) of mib-oid's snmptable is giving
> segmentation fault.
This is fixed by the patch to bug report #2837998
(SVN revision 17857)
See
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/trunk/net-snmp/apps/snm
Hi All,
For some of the value(wrong values ) of mib-oid's snmptable is giving
segmentation fault.
e.g
[r...@localhost make]# snmptable -v 2c -c demopublic localhost .1
Segmentation fault
[r...@localhost make]# snmptable -v 2c -c demopublic localhost .2
Was that a table? joint-iso-cci
Hi all,
I used mib2c.iterate_access.conf to generate my template code. (net-enmp 5.1.1)
I find that if it return NULL in get_ routine, there will be a segmentation
fault.
Is it a normal result?
If it can *not* return NULL in get_ routine, how can I indivate there's an
error occured
On Mon, Apr 27, 2009 at 1:20 PM, sanjaykumar
wrote:
> I am facing following following crash problem .....Segmentation fault (core
> dumped)
>
> following is the trace file
> Please suggest me , what could be the reason for this
You should first analyze your program with Valgri
Hi
I am facing following following crash problem .Segmentation fault
(core dumped)
following is the trace file
Please suggest me , what could be the reason for this
Thanks and regards,
Sanjay
gdb ./packetcable_mta core.28328
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation
.4.2.1
Program received signal SIGSEGV, Segmentation fault.
0xd410 in ?? ()
(gdb) print HRFS_entry
$1 = 538191076
(gdb) print *HRFS_entry
$2 = 538188396
(gdb) print storage_type_id
$3 = {1, 3, 6, 1, 2, 1, 25, 2, 1, 1}
(gdb) print storage_type_len
$4 = 10
(gdb) print storage_type_id[ storage_t
2009/4/8 down Load :
> Program received signal SIGSEGV, Segmentation fault.
> 0xd410 in ?? ()
Hmmm that's not really very informative.
I'd hoped to get something a little more meaningful as to exactly which
line was triggering the problem.
> 4) (gdb) print HRFS_ent
:00 gdb snmpd
root 3408016 1179872 0 17:36:58 pts/1 0:00 /usr/local/sbin/snmpd -f -Le
3) when run snmpget error show like below
Program received signal SIGSEGV, Segmentation fault.
0xd410 in ?? ()
4) (gdb) print HRFS_entry
$1 = 538197124
(gdb) print *HRFS_entry
$2 = 53819
(gdb) pr
2009/4/8 down Load :
> 1) /usr/local/sbin/snmpd -f -Le -Dall
> trace: header_hrstoreEntry(): host/hr_storage.c, 476:
> host/hr_storage: var_hrstoreEntry: process
> HOST-RESOURCES-MIB::hrStorageType.45 ()
> Segmentation fault(coredump)
Yup - that's what I suspe
URCES-MIB::hrStorageType.43
(index 44 HOST-RESOURCES-MIB::hrStorageType.44
(index 45 HOST-RESOURCES-MIB::hrStorageType.45
trace: header_hrstoreEntry(): host/hr_storage.c, 476:
host/hr_storage: var_hrstoreEntry: process HOST-RESOURCES-MIB::hrStorageType.45
(ffff)
Segmentation fault(cor
orageType.45
> host/hr_storage: var_hrstoreEntry: process
> HOST-RESOURCES-MIB::hrStorageType.45 ()
OK - that helps a bit.
We at least know that the problem occurs after this point.
> Segmentation fault(coredump)
Can you please try the following:
1) /usr/local/sbin
2009/4/8 down Load :
> Hi All,
>
> 1) /usr/local/sbin/snmpd -f -Le -D
> /usr/local/sbin/snmpd: option requires an argument -- D
Sorry - that should have been "-Dall"
The point is to turn on *all* debugging output
(as I said yesterday - this is a lot!)
and see what happens just before the crash.
A
-MIB::hrStorageType.45 ()
OK - that helps a bit.
We at least know that the problem occurs after this point.
> Segmentation fault(coredump)
Can you please try the following:
1) /usr/local/sbin/snmpd -f -Le -D
Note that this will produce a *lot* of output.
Wait until it ha
43 .HOST-RESOURCES-MIB::hrStorageType.43
(index 44 HOST-RESOURCES-MIB::hrStorageType.44
(index 45 HOST-RESOURCES-MIB::hrStorageType.45
host/hr_storage: var_hrstoreEntry: process HOST-RESOURCES-MIB::hrStorageType..45
(ffff)
Segmentation fault(coredump)
2)(in a separate terminal).
/usr/
2009/4/6 Dave Shield :
> Can you try re-starting the agent using the command
>
> /usr/local/sbin/snmpd -f -Le -Dhost/hr_storage
>
> and then run
>
> snmpget -v 1 -c public localhost hrStorageDescr..45
>
> again (in a separate terminal).
That last one should have been
snmpget -v 1 -c publi
t -v 1 -c public localhost hrStorageDescr..45
HOST-RESOURCES-MIB::hrStorageDescr.45 = STRING: /oracle/DEV/origlogA
Best Regards,
From: Dave Shield
To: down Load
Cc: [email protected]; [email protected]
Sent: Monday, April 6, 20
2009/4/3 down Load :
> 4)/usr/local/bin#./snmpgetnext -v 1 -c public localhost hrStorageIndex.44
> HOST-RESOURCES-MIB::hrStorageIndex.45 = INTEGER: 45
> 5)/usr/local/bin#./snmpget -v 1 -c public localhost hrStorageIndex.45
> HOST-RESOURCES-MIB::hrStorageIndex.45 = INTEGER: 45
> 6)/usr/local/bin#./s
down Load wrote:
> 7)/usr/local/bin#./snmpget -v 1 -c public localhost hrStorageType.45
> Timeout: No Response from localhost.
> 8)/usr/local/bin#ps -ef|grep snmpd
> root 1134822 3330148 0 17:24:29 pts/1 0:00 grep snmpd
>
> 9)/usr/local/bin#uname -a
> AIX sapdev 3 5 0008B7BED700
Sounds l
ceforge.net
Sent: Friday, April 3, 2009 4:30:32 PM
Subject: Re: Segmentation fault(coredump)
down Load wrote:
> NET-SNMP version 5.4.2.1
What system/OS are you running net-snmp on? ("uname -a)
What's
down Load wrote:
> NET-SNMP version 5.4.2.1
What system/OS are you running net-snmp on? ("uname -a)
What's the output of "net-snmp-config --configure-options"?
+Thomas
--
___
2009/4/3 down Load :
> 2) i run snmpwalk and found
> Received SNMP packet(s) from UDP: [0.0.0.0]->[127.0.0.1]:-26649
> GETNEXT message
> -- HOST-RESOURCES-MIB::hrStorageType.44
> Segmentation fault(coredump)
What is the next entry after row 44?
I.e. what is the output of
Hi All,
1) I run #/usr/local/sbin/snmpd -d -f -L -c /usr/local/share/snmp/snmpd.conf
NET-SNMP version 5.4.2.1
2) i run snmpwalk and found
Received SNMP packet(s) from UDP: [0.0.0.0]->[127.0.0.1]:-26649
GETNEXT message
-- HOST-RESOURCES-MIB::hrStorageType.44
Segmentation fault(cored
[ First - *please* don't mail me directly. Keep discussions on
the list, where others can both learn and offer advice. Thanks. ]
On Thu, 05 Jul 2007 16:53:10 +0530 Ansa wrote:
AA> I wasn't do any debugging .
AA> It was not giving any error messages.Only Segmentat
On Thu, 05 Jul 2007 16:20:56 +0530 Ansa wrote:
AA> I am getting Segmentation Fault while running snmpd in MIPS64 bit
AA> Processor.
We are going to need a little bit more information that you have provided. For
example, a stack trace would be very helpful. Any error messages? When do
Hi,
I am getting Segmentation Fault while running snmpd in MIPS64 bit
Processor.
I have Cross-Compiled the net-snmp-5.4 for MIPS64 bit Processor using
the following configuration Options.
RANLIB=mips64-octeon-linux-gnu-ranlib LD=mips64-octeon-linux-gnu-gcc
./configure --with-cc=mips64
Hi All,
I think the table_info->colnum is not properly set when a
walk/get_next/get is issued for an empty table. The code lines in
question are table_iterator.c Line 706 and Line 747. Kindly provide
feedback. The fault is reproducible by generating a table using mib2c
iterator table configur
Dear net-snmp-coders,
I was able to reproduce RowStatus segmentation fault with
snmpNotifyFilterRowStatus in 5.3.1 master agent.
This problem can be easily reproduced by the following steps:
$ snmpset 10.1 snmpNotifyFilterRowStatus.3.65.66.67.1 i 4
SNMP-NOTIFICATION-MIB
On Thu, 28 Jul 2005 10:42:39 -0500 [EMAIL PROTECTED] wrote:
EYC> Yes, I was running with -Dall option when "Broken pipe" happened. Then
EYC> what is the condition that -Dall will not cause "Broken pipe"?
-D is debug output, but is not actually running under a debugger.
EYC> If running without deb
Robert,
Yes, I was running with -Dall option when "Broken pipe" happened. Then what is the condition that -Dall will not cause "Broken pipe"?
If running without debug option, snmpwalk on etherStatsDataSource works okay now.
Thanks for the patch, it fixed the mib2c oid typ
On Tue, 26 Jul 2005 11:34:37 -0500 [EMAIL PROTECTED] wrote:
EYC> trace: netsnmp_unix_send(): snmpUnixDomain.c, 160:
EYC> netsnmp_unix: send 20 bytes to 0x80bbfe0 on fd 5
EYC> Broken pipe
Were you running in a debugger? A broken pipe would be if either side shut down
the connections (maybe because
forge.net
To
[EMAIL PROTECTED]
cc
[email protected]
Subject
Re: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource
On Fri, 22 Jul 2005 13:21:46 -0500 [EMAIL PROTECTED] wrote:
Not to non-zero, but something greater than 10.
I don't know
e strange thing is if I not set etherStatsDataSource_len, the subagent
EYC> works just fine. Only when I set etherStatsDataSource_len to none-zero it
EYC> causes segmentation fault.
Not to non-zero, but something greater than 10.
I don't know how I haven't run across this in my
e: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource
On Thu, 21 Jul 2005 08:10:38 -0500 [EMAIL PROTECTED] wrote:
> what release are you running?
I am using 5.2.1 release.
> Did you accept all the defaults?
I accepted all the defaults except the last question I c
On Thu, 21 Jul 2005 08:10:38 -0500 [EMAIL PROTECTED] wrote:
EYC> It's easy to reproduce the problem in two steps:
For you, maybe, not for me. I should have asked before, what release are you
running?
EYC> 1. Generate mib2c template for etherStatsTable using mib2c.mfd.conf ,
Did you accept all th
Robert Story <[EMAIL PROTECTED]>
07/21/2005 06:52 AM
Please respond to
[email protected]
To
[EMAIL PROTECTED]
cc
[email protected]
Subject
Re: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource
On Wed, 20 J
On Wed, 20 Jul 2005 10:47:33 -0500 [EMAIL PROTECTED] wrote:
EYC> This is hard-coded just as the piece of code I copy&pasted in my email.
Ok, where is it? What function?
EYC> RMON-MIB::etherStatsDataSource = Wrong Type (should be OBJECT IDENTIFIER):
EYC> Variable has bad type
Which is odd, since
net
Subject
Re: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource
On Wed, 20 Jul 2005 09:32:59 -0500 [EMAIL PROTECTED] wrote:
EYC> I have implemented several subagents for BRIDGE-MIB tables using mib2c and
EYC> mib2c.mfd.conf. They all worked well. Now I came acr
If I
EYC> don't set etherStatsDataSource and let it be the default 0.0, the
EYC> etherStatsTable subagent works okay. But if I set etherStatsDataSource_len
EYC> to something not 0 (such as in the following code), it will cause
EYC> segmentation fault. Here is the code which set e
, the etherStatsTable subagent works okay. But if I set etherStatsDataSource_len to something not 0 (such as in the following code), it will cause segmentation fault. Here is the code which set etherStatsDataSource in etherStatsTable_cache_load(netsnmp_container * container):
oid etherStatsDataS
On Wed, 20 Oct 2004 18:19:52 +0530 Karthikeyan wrote:
KN> I am using netsnmp5.2Pre3 release in linux enviornment. I am getting the
KN> following segementation fault when I run the agent (after including
KN> ifXTable support):
KN>
KN> netsnmp_assert ((void *)0) != _ifXTable_container_get() failed
K
() failed
if-mib/ifXTable/ifXTable.c:112 initialize_table_ifXTable()
Segmentation fault
Initially I used configure script by adding ifXTable mib modules such as follows:
./configure -with-mib-modules="if-mib/ifTable if-mib/ifXTable"
Then, I rn make and make install.
Please let me know is
59 matches
Mail list logo
