Dont understand backtrace output

Dont understand backtrace output

[Joshua_Giles]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

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
#2  0x40038248 in handle_var_list () at eval.c:41
#3  0x40038183 in handle_next_pass () at eval.c:41
#4  0x40037e3f in handle_snmp_packet () at eval.c:41
#5  0x400f799b in _sess_read () at eval.c:41
#6  0x400f7a10 in snmp_sess_read () at eval.c:41
#7  0x400f6dca in snmp_read () at eval.c:41
8  0x0804b2fb in SnmpdDump () at eval.c:41
#9  0x0804ac85 in SnmpdDump () at eval.c:41
#10 0x4023b507 in __libc_start_main (main=0x8049e50 <SnmpdDump+96>,
argc=9, ubp_av=0xbffff944,
    init=0x804960c <_init>, fini=0x804ba10 <_fini>, rtld_fini=0x4000dc14
<_dl_fini>,
    stack_end=0xbffff93c) at ../sysdeps/generic/libc-start.c:129
>>

I really don't think eval.c is where the problem lies.  

Regards,




Joshua Giles
PG Software Engineer Sr. Analyst
Joshua_Giles@dell.com
Linux website @ dell => www.dell.com/linux

Re: Dont understand backtrace output

[H . J . Lu]

[-- 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.

Re: Dont understand backtrace output

[Andreas Jaeger]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

Joshua_Giles@Dell.com writes:

> 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)

<stdlib.h> on glibc 2 systems has:
extern __inline long int
strtol (__const char *__restrict __nptr, char **__restrict __endptr,
        int __base) __THROW
{
  return __strtol_internal (__nptr, __endptr, __base, 0);
}

The values for group and base look wrong, it might be that those are
not initialized (yet).

I would check what eval.c does here.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Dont understand backtrace output

[Kevin Buettner]

On Sep 17, 10:13am, Joshua_Giles@Dell.com wrote:

> Can anyone give me the lowdown on what this output means in gdb,
> specifically the
> "__strtol_internal" line.
> 
[...]
> __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
> #2  0x40038248 in handle_var_list () at eval.c:41
> #3  0x40038183 in handle_next_pass () at eval.c:41
> #4  0x40037e3f in handle_snmp_packet () at eval.c:41
> #5  0x400f799b in _sess_read () at eval.c:41
> #6  0x400f7a10 in snmp_sess_read () at eval.c:41
> #7  0x400f6dca in snmp_read () at eval.c:41
> 8  0x0804b2fb in SnmpdDump () at eval.c:41
> #9  0x0804ac85 in SnmpdDump () at eval.c:41
> #10 0x4023b507 in __libc_start_main (main=0x8049e50 <SnmpdDump+96>,
> argc=9, ubp_av=0xbffff944,
>     init=0x804960c <_init>, fini=0x804ba10 <_fini>, rtld_fini=0x4000dc14
> <_dl_fini>,
>     stack_end=0xbffff93c) at ../sysdeps/generic/libc-start.c:129
> >>
> 
> I really don't think eval.c is where the problem lies.

I agree with you.  (It does seem highly improbable that all of the above
calls occur from eval.c, line 41, doesn't it?) 

Please try a development version of GDB and let me know if you
still see this problem.  I believe this problem is fixed by
the following changes committed 2001-09-06:

	* dbxread.c (process_one_symbol): Don't use error result from
	find_stab_function_addr().
	* partial-stab.h (case 'F'): Likewise.

	* partial-stab.h (case 'f'): Make SOFUN_ADDRESS_MAYBE_MISSING
	code match that used for case 'F'.  This fixes the divergence
	that was introduced by my 1999-09-14 changes to partial-stab.h.

We are attempting to decide if the above changes ought to go in
the 5.1 branch, so your feedback would be really helpful...

See http://sources.redhat.com/gdb/download/ for information about
downloading a development version of GDB.