From: Jason Molenda <jmolenda@apple.com>
To: Louis LeBlanc <leblanc@keyslapper.net>
Cc: gdb@sources.redhat.com
Subject: Re: stack corruption?
Date: Tue, 14 Jun 2005 20:36:00 -0000 [thread overview]
Message-ID: <10DBEAA7-48B2-4298-A8CC-58A138415516@apple.com> (raw)
In-Reply-To: <20050614033256.GB48802@keyslapper.net>
On Jun 13, 2005, at 8:32 PM, Louis LeBlanc wrote:
> Stack corruption shows up anytime I open the program in gdb. I get an
> occasional core dump (SEGV and BUS) from my program, but when I can
> make heads or tails of it, it appears to be deep in a host lookup
> (system libs, Solaris 9) or Oracle 8.1.7 database calls (which could
> also be a host lookup).
Louis, I think you're going to need to be a lot more specific.
You're using gdb on Solaris 9 with a SPARC CPU? What version of
gdb? Your paragraph above sounds like there's a bug in your program
causing it to crash, and you cannot understand the stack backtrace --
are you asking for help in using gdb to find your bug, or are you
saying that gdb is not behaving properly?
If it's the latter, some example output of the problem would do
wonders to clear things up.
Jason
next prev parent reply other threads:[~2005-06-14 20:36 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 [this message]
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
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=10DBEAA7-48B2-4298-A8CC-58A138415516@apple.com \
--to=jmolenda@apple.com \
--cc=gdb@sources.redhat.com \
--cc=leblanc@keyslapper.net \
/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