From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] acid analogues of gdb stepping commands
Date: Fri, 8 Nov 2013 18:51:54 -0500 [thread overview]
Message-ID: <c18c95ec163f211e43c7320ed244e53c@ladd.quanstro.net> (raw)
In-Reply-To: <20131108234629.GO11218@iota.offblast.org>
> this seems like it should work, but sometimes the computed PC for the
> next line is way off, and cont() just runs the entire program. even more
> confusing, doing pcline of the computed pc prints the next line
> correctly, e.g.
>
> x = filepc(pcfile(*PC)+":"+itoa(pcline(*PC)+1));
> print(pcline(x));
>
> will show the next line, but the new PC in x is totally wrong.
>
> any clue why?
have you tried compiling with -N (no peephole opt).
- erik
next prev parent reply other threads:[~2013-11-08 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 2:46 Nick Owens
2013-11-08 7:40 ` Skip Tavakkolian
2013-11-08 10:03 ` Skip Tavakkolian
2013-11-08 23:46 ` Nick Owens
2013-11-08 23:51 ` erik quanstrom [this message]
2013-11-09 0:36 ` Nick Owens
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=c18c95ec163f211e43c7320ed244e53c@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).