From: Daniel Jacobowitz <drow@mvista.com>
To: "Kremer Markus (MPI/SFR)" <Markus.Kremer@tenovis.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: wrong backtrace / __JCR_LIST__ instead of real function name
Date: Tue, 21 Oct 2003 12:54:00 -0000 [thread overview]
Message-ID: <20031021125420.GB21053@nevyn.them.org> (raw)
In-Reply-To: <C3328C09441A4840A81D23C6F2590B5A13F799@tndefr-ws00022.tenovis.corp.lan>
On Tue, Oct 21, 2003 at 01:05:34PM +0200, Kremer Markus (MPI/SFR) wrote:
> Hello,
> i am using gcc 3.2 and gdb 5.3.
> One thread of my programm calls
> pthread_start_thread->wrapper_routine->acom_loop->acom->acom_read->select.
>
> When i debug my application i get strange backtraces.
> instead of acom_read() __JCR_LIST__() is displayed in frame #1.
>
> I had similar problems at other places in my code.
> When i used gcc 2.9x and gdb 5.2 i had the same problems.
>
> Any clues what went wrong?
> ....
> pressing CTRL-C
> ....
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 3076 (LWP 26480)]
> 0x401ad6ae in select () from
> //app/i33tools/gcc/gcc-3.2c/i386-linux/lib/libc.so.6
> (gdb) bt
> #0 0x401ad6ae in select () from
> //app/i33tools/gcc/gcc-3.2c/i386-linux/lib/libc.so.6
> #1 0x0805e9cc in __JCR_LIST__ ()
This means GDB couldn't figure out how to backtrace from select. It's
an assembly wrapper, so it's hard to manually figure out the frame
location.
Recent versions of gdb and binutils support annotating assembly
functions to describe the backtrace. Most libc functions will
eventually be annotated, since NPTL uses this information also.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-21 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 11:05 Kremer Markus (MPI/SFR)
2003-10-21 12:54 ` Daniel Jacobowitz [this message]
2003-10-21 14:21 Michael Elizabeth Chastain
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=20031021125420.GB21053@nevyn.them.org \
--to=drow@mvista.com \
--cc=Markus.Kremer@tenovis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).