Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Function argument no longer in register
Date: Mon, 29 Mar 2004 14:44:00 -0000	[thread overview]
Message-ID: <40683636.4060906@axis.com> (raw)
In-Reply-To: <20040329142536.GA14990@nevyn.them.org>

Daniel Jacobowitz wrote:
>>
>>I don't know what kind of problem I'm looking at here.  Could it be that 
>>the debug information is wrong?  I'm guessing GDB somehow fails to 
>>realize that the function argument is out of scope at this point.
> 
> 
> Nothing's wrong - eventually, versions of GCC with proper location list
> will tell GDB that the variable is out of scope, but no released
> version does that.  I think 3.5 snapshots will.

Ah, ok.  Thanks.  The setup is a remote stub debugging a Linux kernel, 
and the first page (8k for CRIS) is read/write-protected.  So, I guess I 
need to filter out these bogus reads in the stub to prevent the kernel 
from oopsing.

-- 
Orjan Friberg
Axis Communications


      reply	other threads:[~2004-03-29 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 14:21 Orjan Friberg
2004-03-29 14:25 ` Daniel Jacobowitz
2004-03-29 14:44   ` Orjan Friberg [this message]

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=40683636.4060906@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=drow@false.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