From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: thread apply all - not working?
Date: Fri, 27 May 2005 19:57:00 -0000 [thread overview]
Message-ID: <20050527195735.GA20173@nevyn.them.org> (raw)
In-Reply-To: <20050527194956.GG59006@keyslapper.net>
On Fri, May 27, 2005 at 03:49:56PM -0400, Louis LeBlanc wrote:
> (gdb) thread apply all bt
>
> Thread 104 (process 6772575 ):
> #0 0xfea1e574 in __tbl_2_big_digits () from /usr/lib/libc.so.1
> #1 0xff34db00 in read () from /usr/lib/lwp/libthread.so.1
> #2 0xfef86960 in snttread () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #3 0xfef842f0 in nttrd () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #4 0xfee3ec2c in nsprecv () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #5 0xfee43740 in nsrdr () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #6 0xfee2968c in nsdo () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #7 0xfeeafb74 in nioqrc () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #8 0xfefffe54 in ttcdrv () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #9 0xfeeb81e0 in nioqwa () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #10 0xfed3b5cc in upirtrc () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #11 0xfed8b64c in kpurcsc () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #12 0xfed5b104 in kpuexecv8 () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #13 0xfed5d2d4 in kpuexec () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #14 0xfed9a318 in OCIStmtExecute () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #15 0x000e5234 in execute_statement (connID=1533288, stmntID=3, args=0xf837a650, dbTimingRec=0xf8379b80, inOpCode=18758) at dbase.c:873
> #16 0x0002f1dc in handle_check (thread=0x759b30) at miniget.c:1044
> #17 0x000e3134 in spawn (arg=0x759b30) at xpcthread.c:195
> #18 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
> #19 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
> Previous frame identical to this frame (corrupt stack?)
> #0 0xff024044 in ttcpip () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
That's the problem. It's an error message; it stops "thread apply"
from continuing.
Jeff Johnston fixed this in CVS on 2004-11-05; try a CVS HEAD snapshot.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-27 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 18:45 Louis LeBlanc
2005-05-27 19:15 ` Daniel Jacobowitz
2005-05-27 19:24 ` Louis LeBlanc
2005-05-27 19:30 ` Daniel Jacobowitz
2005-05-27 19:49 ` Louis LeBlanc
2005-05-27 19:57 ` Daniel Jacobowitz [this message]
2005-05-27 20:13 ` Louis LeBlanc
2005-05-28 0:12 ` Daniel Jacobowitz
2005-05-27 20:18 ` Louis LeBlanc
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=20050527195735.GA20173@nevyn.them.org \
--to=drow@false.org \
--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