From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: stack corruption?
Date: Tue, 14 Jun 2005 02:01:00 -0000 [thread overview]
Message-ID: <20050614020138.GA19453@nevyn.them.org> (raw)
In-Reply-To: <20050614014520.GG24814@keyslapper.net>
On Mon, Jun 13, 2005 at 09:45:20PM -0400, Louis LeBlanc wrote:
> This might be a bit of a trivial question, but I am having trouble
> with stack corruption.
>
> I started seeing this after I began using gcc 3.3 with the -ggdb -g3
> flags to try to provide more detailed info for gdb. Can anyone tell
> me how these flags change the executable?
>
> Without the -ggdb switch, I don't get any debugging symbols at all.
>
> Anyone have any ideas what else I should be looking at?
Stack corruption in your program, or in GDB? Neither should change the
generated code at all. -g3 adds macro debugging information.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-14 2:01 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 [this message]
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
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=20050614020138.GA19453@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