edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] page code overloading sw
Date: Mon, 02 Sep 2019 22:17:54 -0400	[thread overview]
Message-ID: <20190802221754.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1909021852320.38563@phoenix>

[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

Note this paragraph from my debugging page in the wiki.
This may be what is happening.


I worked on one site that added its own toString() functions to various prototypes, and these in turn had trace points,
so when I asked for the value of x, and it tried to turn x into a string, it entered the toString() function associated with x, which triggered more breakpoints, which was really really confusing.
I entered . . . and finally got back to the string value of x.
I hope this is a rare occurrence.

Karl Dahlke

      reply	other threads:[~2019-09-03  2:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  1:58 Kevin Carhart
2019-09-03  2:17 ` Karl Dahlke [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190802221754.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).