Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: [CRIS] dwarf2 frame sniffer problem?
Date: Wed, 10 Mar 2004 16:53:00 -0000	[thread overview]
Message-ID: <404F481E.9060709@axis.com> (raw)

After getting the CRIS port into shape without the dwarf2 frame sniffer, 
I hooked it in and found that basic stuff like next over a function call 
no longer works.  (More specifically, after stepping into the function, 
gdb sets the breakpoint on the jump instruction itself, rather than at 
the instruction after.)

I do get a complaint "During symbol reading, Incomplete CFI data; 
unspecified registers at 0x000802f6." already by the time I get to 
main(), where 802f6 is the first address in main(), which is where the 
subroutine pointer is pushed.  Although there is a comment in 
dwarf2-frame.c explaining the complaint, I'm not sure how seriously I 
should take it.

Thanks for any idea on what might be the cause or where to start digging.

-- 
Orjan Friberg
Axis Communications


WARNING: multiple messages have this Message-ID
From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: [CRIS] dwarf2 frame sniffer problem?
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <404F481E.9060709@axis.com> (raw)
Message-ID: <20040319000900.JGtsHITDuuk5WBNeH8IshWq2qjse_VLIkSs7LzbYJf4@z> (raw)

After getting the CRIS port into shape without the dwarf2 frame sniffer, 
I hooked it in and found that basic stuff like next over a function call 
no longer works.  (More specifically, after stepping into the function, 
gdb sets the breakpoint on the jump instruction itself, rather than at 
the instruction after.)

I do get a complaint "During symbol reading, Incomplete CFI data; 
unspecified registers at 0x000802f6." already by the time I get to 
main(), where 802f6 is the first address in main(), which is where the 
subroutine pointer is pushed.  Although there is a comment in 
dwarf2-frame.c explaining the complaint, I'm not sure how seriously I 
should take it.

Thanks for any idea on what might be the cause or where to start digging.

-- 
Orjan Friberg
Axis Communications


             reply	other threads:[~2004-03-10 16:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 16:53 Orjan Friberg [this message]
2004-03-10 16:59 ` Daniel Jacobowitz
2004-03-19  0:09   ` Daniel Jacobowitz
2004-03-19  0:09   ` Orjan Friberg
2004-03-11 14:09     ` Orjan Friberg
2004-03-11 15:55     ` Orjan Friberg
2004-03-11 17:05       ` Andrew Cagney
2004-03-19  0:09         ` Orjan Friberg
2004-03-12 12:00           ` Orjan Friberg
2004-03-19  0:09         ` Andrew Cagney
2004-03-11 17:11       ` Daniel Jacobowitz
2004-03-12 10:23         ` Orjan Friberg
2004-03-19  0:09           ` Orjan Friberg
2004-03-12 15:38             ` Orjan Friberg
2004-03-19  0:09           ` Orjan Friberg
2004-03-12 13:50             ` Orjan Friberg
2004-03-19  0:09           ` Orjan Friberg
2004-03-19  0:09           ` Daniel Jacobowitz
2004-03-12 15:38             ` Daniel Jacobowitz
2004-03-15 10:19             ` Orjan Friberg
2004-03-19  0:09               ` Orjan Friberg
2004-03-16 16:26             ` Orjan Friberg
2004-03-16 19:13               ` Daniel Jacobowitz
2004-03-16 20:51                 ` Hans-Peter Nilsson
2004-03-16 22:27                   ` Daniel Jacobowitz
2004-03-16 23:38                     ` Hans-Peter Nilsson
2004-03-16 23:58                       ` Daniel Jacobowitz
2004-03-19  0:09                         ` Daniel Jacobowitz
2004-03-19  0:09                       ` Hans-Peter Nilsson
2004-03-19  0:09                     ` Daniel Jacobowitz
2004-03-19  0:09                   ` Hans-Peter Nilsson
2004-03-19  0:09                 ` Daniel Jacobowitz
2004-03-19  0:09               ` Orjan Friberg
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-19  0:09       ` Orjan Friberg
2004-03-19  0:09 ` Orjan Friberg

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=404F481E.9060709@axis.com \
    --to=orjan.friberg@axis.com \
    --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