From: Daniel Jacobowitz <drow@false.org>
To: NZG <ngustavson@emacinc.com>
Cc: gdb-patches@sourceware.org,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: gdb code review, pointer madness
Date: Mon, 23 Jan 2006 20:48:00 -0000 [thread overview]
Message-ID: <20060123204804.GA28608@nevyn.them.org> (raw)
In-Reply-To: <200601231438.26040.ngustavson@emacinc.com>
On Mon, Jan 23, 2006 at 02:38:25PM -0600, NZG wrote:
> I'm trying to get gdb 6.1's machine interface to work correctly with the m68k
> arch, and I'm having some weird results.
>
> I've noticed that if I do a (frame -1) command on gdb after connecting to
> remote gdb server, but before breaking in the main program, gdb goes crazy
> and starts requesting random memory locations from gdbserver until something
> crashes.
>
> Sooo... I'm using regular gdb to debug the m68k-elf-gdb connection, and I'm
> seeing a problem "extract_unsigned_integer" (pasted below).
>
> Specifically this loop doesn't seem to be executing correctly
>
> for (p = startaddr; p < endaddr; ++p)
> retval = (retval << 8) | *p;
>
> In the function call I'm watching,
> endaddr = startaddr+4,
> yet, when I step through the function the loop executes 8 times and overshoots
> the array.
You are probably just debugging optimized code. Either that, or your
host compiler is completely broken; the loop is correct.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-23 20:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 20:39 NZG
2006-01-23 20:48 ` Daniel Jacobowitz [this message]
2006-01-23 20:51 ` Jim Blandy
2006-01-24 17:19 ` NZG
2006-01-24 19:29 ` NZG
2006-01-24 21:27 ` Jim Blandy
2006-01-24 21:58 ` NZG
2006-01-24 22:11 ` Daniel Jacobowitz
2006-01-25 0:01 ` Jim Blandy
2006-01-25 4:41 ` Eli Zaretskii
2006-01-25 4:59 ` Jim Blandy
2006-01-25 5:25 ` Jim Blandy
2006-01-25 17:21 ` Eli Zaretskii
2006-01-25 18:49 ` Jim Blandy
2006-01-25 19:58 ` Eli Zaretskii
2006-01-25 17:15 ` Eli Zaretskii
2006-01-26 16:19 ` NZG
2006-01-26 16:43 ` Daniel Jacobowitz
2006-01-26 19:55 ` frame theory, was " NZG
2006-01-26 19:59 ` Daniel Jacobowitz
2006-01-26 20:17 ` NZG
2006-01-26 20:22 ` Daniel Jacobowitz
2006-01-26 21:21 ` Mark Kettenis
2006-01-26 21:54 ` NZG
2006-01-26 22:40 ` Mark Kettenis
2006-01-26 22:44 ` Daniel Jacobowitz
2006-01-26 23:27 ` remote connection crash, was frame theory NZG
2006-01-26 23:32 ` Daniel Jacobowitz
2006-01-26 23:42 ` Jim Blandy
2006-01-26 23:45 ` Daniel Jacobowitz
2006-01-26 23:57 ` Jim Blandy
2006-01-27 0:04 ` NZG
2006-01-30 17:02 ` 5282 gdb Eclipse MI support, was remote connection crash NZG
2006-01-26 23:47 ` frame theory, was pointer madness Accounts
2006-01-26 23:16 ` Jim Blandy
2006-01-26 23:39 ` Jim Blandy
2006-01-27 7:19 ` 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=20060123204804.GA28608@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=ngustavson@emacinc.com \
--cc=uclinux-dev@uclinux.org \
/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