From: "H . J . Lu" <hjl@lucon.org>
To: Joshua_Giles@Dell.com
Cc: gdb@sources.redhat.com
Subject: Re: Dont understand backtrace output
Date: Mon, 17 Sep 2001 08:20:00 -0000 [thread overview]
Message-ID: <20010917082020.A17665@lucon.org> (raw)
In-Reply-To: <E97B8CCBF670D511A8BE009027457F14044A5E@ausxmrr501.us.dell.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On Mon, Sep 17, 2001 at 10:13:55AM -0500, Joshua_Giles@Dell.com wrote:
> Hi all,
>
> Can anyone give me the lowdown on what this output means in gdb,
> specifically the
> "__strtol_internal" line.
>
> >>
> Starting program: /usr/sbin/snmpd -f -L -s -l /dev/null -P /var/run/snmpd
> -a
> (no debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...
> UCD-SNMP version 4.2.1
> [smux_accept] accepted fd 8 from 127.0.0.1:32944
> accepted smux peer: oid çZ0@?Ãÿ¿ÿÿÿÿTQ5@@Ãÿ¿, password , descr Dell
> OpenManage Server Agent
> Received SNMP packet(s) from 10.180.93.160
> (no debugging symbols found)...
> Program received signal SIGSEGV, Segmentation fault.
>
> __strtol_internal (nptr=0x80c22f0 "", endptr=0x8134878, base=1074899065,
> group=1073971726)
> at eval.c:36
> 36 eval.c: No such file or directory.
> in eval.c
> (gdb) bt
> #0 __strtol_internal (nptr=0x80c22f0 "", endptr=0x8134878,
> base=1074899065, group=1073971726)
> at eval.c:36
> #1 0x40038498 in handle_one_var () at eval.c:41
You have 2 eval.c, one in glibc and the other in your application.
__strtol_internal is in eval.c from glibc. It looks like the call
to __strtol_internal is wrong.
H.J.
next prev parent reply other threads:[~2001-09-17 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 8:14 Joshua_Giles
2001-09-17 8:20 ` H . J . Lu [this message]
2001-09-17 8:21 ` Andreas Jaeger
2001-09-17 10:15 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010917082020.A17665@lucon.org \
--to=hjl@lucon.org \
--cc=Joshua_Giles@Dell.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox