Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrea Michelotti <amichelotti@ipitec.it>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@redhat.com>,
	gdb-patches@sources.redhat.com,
	Michael Snyder <msnyder@redhat.com>
Subject: Re: patch for info threads problem with target arm-elf (PR 1199).
Date: Mon, 28 Jul 2003 10:17:00 -0000	[thread overview]
Message-ID: <3F24F903.5080308@ipitec.it> (raw)
In-Reply-To: <20030726021548.GA22833@nevyn.them.org>

Daniel Jacobowitz wrote:

>On Fri, Jul 25, 2003 at 10:10:40PM -0400, Andrew Cagney wrote:
>  
>
>>>-  /* Avoid coredumps which would happen if we tried to access a NULL
>>>-     deprecated_selected_frame.  */
>>>-  if (!target_has_stack)
>>>-    error ("No stack.");
>>>+  /* Check that there really is a frame.  This happens when a simulator
>>>+     is connected but not loaded or running, for instance.  */
>>>+  if (saved_frame_level < 0)
>>>+    error ("No frame.");
>>>      
>>>
>>This would only happen to old architectures (legacy_get_prev_frame). 
>>With new architectures (get_prev_frame), frame creation is so lazy that 
>>an inner most frame is (hopefully?) always created.  Can you make this 
>>check conditional on legacy_frame_p?
>>    
>>
>
>Ah, that's the bit I was missing.  Thanks, sounds reasonable to me.
>
>  
>
I've tried the patch, it's ok.
thanks.
ciao
Andrea.

--------------------------------------
Andrea Michelotti 
HW/SW Co-Design Manager
IPITEC (ATMEL) 






  reply	other threads:[~2003-07-28 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 16:43 Andrea Michelotti
2003-07-26  0:26 ` Michael Snyder
2003-07-26  0:29   ` Daniel Jacobowitz
2003-07-26  1:26     ` Andrew Cagney
2003-07-26  1:48       ` Daniel Jacobowitz
2003-07-26  2:10         ` Andrew Cagney
2003-07-26  2:15           ` Daniel Jacobowitz
2003-07-28 10:17             ` Andrea Michelotti [this message]
2003-07-28 13:03             ` Daniel Jacobowitz

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=3F24F903.5080308@ipitec.it \
    --to=amichelotti@ipitec.it \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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