Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Joshua_Giles@Dell.com, gdb@sources.redhat.com
Cc: Elena Zannoni <ezannoni@cygnus.com>
Subject: Re: Dont understand backtrace output
Date: Mon, 17 Sep 2001 10:15:00 -0000	[thread overview]
Message-ID: <1010917171508.ZM9879@ocotillo.lan> (raw)
In-Reply-To: <E97B8CCBF670D511A8BE009027457F14044A5E@ausxmrr501.us.dell.com>

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.


      parent reply	other threads:[~2001-09-17 10:15 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
2001-09-17  8:21 ` Andreas Jaeger
2001-09-17 10:15 ` Kevin Buettner [this message]

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=1010917171508.ZM9879@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=Joshua_Giles@Dell.com \
    --cc=ezannoni@cygnus.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