From: Louis LeBlanc <leblanc@keyslapper.net>
To: gdb@sources.redhat.com
Subject: Re: stack corruption?
Date: Tue, 14 Jun 2005 22:09:00 -0000 [thread overview]
Message-ID: <20050614220919.GA43494@keyslapper.net> (raw)
In-Reply-To: <200506142144.j5ELi9ew013949@elgar.sibelius.xs4all.nl>
On 06/14/05 11:44 PM, Mark Kettenis sat at the `puter and typed:
> <SNIP>
> #0 0xff024044 in ttcpip () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> (gdb) bt
> #0 0xff024044 in ttcpip () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #1 0xff000470 in ttcdrv () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #2 0xfeeb81e0 in nioqwa () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #3 0xfed3b5cc in upirtrc () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #4 0xfed8b64c in kpurcsc () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #5 0xfed5b104 in kpuexecv8 () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #6 0xfed5d2d4 in kpuexec () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #7 0xfed9a318 in OCIStmtExecute () from /opt/oracle/8.1.7/lib/libclntsh.so.8.0
> #8 0x000e5234 in execute_statement (connID=1649752, stmntID=1, args=0xf827a650, dbTimingRec=0xf8279b80, inOpCode=19541) at dbase.c:873
> #9 0x0002e9f4 in handle_check (thread=0x759b70) at myprog.c:904
> #10 0x000e3134 in spawn (arg=0x759b70) at mythread.c:195
> #11 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
> #12 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
> Previous frame identical to this frame (corrupt stack?)
> (gdb)
>
> I have changed identifying names to protect the guilty, but this is
> pretty much typical.
>
> Oh, that's pretty harmless. It's gdb falling off the end of the
> stack. Ideally gdb would now that it reached the end of the stack,
> and not print the message. But I haven't found a reliable way to do
> so for Solaris SPARC. But then I haven't really tried very hard.
Ah. Well, I'm glad this isn't something wrong with my code. Problem
is it makes applying some commands to all threads difficult.
Thanks for the clarification.
Lou
--
Louis LeBlanc dev@keyslapper.net
Fully Funded Hobbyist, KeySlapper Extrordinaire :þ
http://www.keyslapper.net Ô¿Ô¬
Key fingerprint = C5E7 4762 F071 CE3B ED51 4FB8 AF85 A2FE 80C8 D9A2
Boren's Laws:
(1) When in charge, ponder.
(2) When in trouble, delegate.
(3) When in doubt, mumble.
next prev parent reply other threads:[~2005-06-14 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 1:45 Louis LeBlanc
2005-06-14 2:01 ` Daniel Jacobowitz
2005-06-14 3:33 ` Louis LeBlanc
2005-06-14 20:36 ` Jason Molenda
2005-06-14 20:52 ` Louis LeBlanc
2005-06-14 21:24 ` Mark Kettenis
2005-06-14 21:31 ` Louis LeBlanc
2005-06-14 21:36 ` Jason Molenda
2005-06-14 21:44 ` Mark Kettenis
2005-06-14 22:09 ` Louis LeBlanc [this message]
2005-06-14 22:35 ` Daniel Jacobowitz
2005-06-14 21:26 ` Jason Molenda
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=20050614220919.GA43494@keyslapper.net \
--to=leblanc@keyslapper.net \
--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