From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] problem fetching inferior memory due to breakpoint
Date: Sat, 29 Apr 2006 14:20:00 -0000 [thread overview]
Message-ID: <20060429142037.GA20825@nevyn.them.org> (raw)
In-Reply-To: <uhd4cfp0i.fsf@gnu.org>
On Sat, Apr 29, 2006 at 05:13:49PM +0300, Eli Zaretskii wrote:
> Here's what I get (from the .s file written by the above GCC command):
>
> .file "gdbt.c"
> .section .debug_abbrev,"dr"
> Ldebug_abbrev0:
> .section .debug_info,"dr"
> Ldebug_info0:
> .section .debug_line,"dr"
> Ldebug_line0:
> .text
> Ltext0:
> .section .rdata,"dr"
> LC0:
> .ascii "Hello world.\12\0"
> .text
> .globl _hello
> .def _hello; .scl 2; .type 32; .endef
> _hello:
> LFB10:
> .file 1 "gdbt.c"
> .loc 1 5 0
> pushl %ebp
That's why. Your Cygwin compiler uses DWARF-2 unwinding; therefore the
prologue analyzer is never even invoked. Try using -gstabs instead of
-gdwarf-2 (or not using -g at all), and I bet you'll see the problem.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-29 14:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 19:05 Joel Brobecker
2006-04-26 19:19 ` Daniel Jacobowitz
2006-04-26 21:18 ` Joel Brobecker
2006-04-26 21:39 ` Daniel Jacobowitz
2006-04-26 22:18 ` Joel Brobecker
2006-04-26 22:29 ` Daniel Jacobowitz
2006-04-26 23:33 ` Michael Snyder
2006-04-27 0:42 ` Daniel Jacobowitz
2006-04-27 1:37 ` Michael Snyder
2006-04-27 2:10 ` Daniel Jacobowitz
2006-04-27 0:53 ` Jim Blandy
2006-04-27 20:28 ` Eli Zaretskii
2006-04-27 20:56 ` Joel Brobecker
2006-04-28 5:12 ` Eli Zaretskii
2006-04-28 17:00 ` Joel Brobecker
2006-04-28 17:45 ` Daniel Jacobowitz
2006-04-29 14:14 ` Eli Zaretskii
2006-04-29 14:20 ` Daniel Jacobowitz [this message]
2006-04-29 14:48 ` Eli Zaretskii
2006-04-29 15:06 ` Daniel Jacobowitz
2006-04-29 15:18 ` Daniel Jacobowitz
2006-04-29 17:10 ` Eli Zaretskii
2006-04-29 14:14 ` Eli Zaretskii
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=20060429142037.GA20825@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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