From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Subject: [Edbrowse-dev] the amazon saga
Date: Mon, 8 Jan 2018 11:11:14 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801081058410.3263@debian.pulsar.com> (raw)
Karl,
Well I have a log for you to look at, and I will too, but first:
I followed your steps, and quickly got the initial raw html size, at
which point the size of /tmp/log was about 2k with only 54 lines, and it
stayed that way. The rendered size was never displayed. But when, out of
curiosity, I pressed "=" and enter, it gave a size of about 5k if I
recall. It will no doubt be in the log.
Next I pressed enter and got "end of buffer" so I typed 1 enter and got
an html header line.
Undaunted, I typed b enter, and at first it seemed like nothing
happened.
However the log file now showed some 80K lines and a multi MB size, so I
then examined the contents of my edbrowse session, and I found a good
looking Amazon opening screen.
I found the usual stuff on line 11, did a g2,
added my email address and password, submitted, and got a segfault.
I suppressed my password with a global replace, and posted the log at:
www.panix.com/~chuxroom/amazon.chuck.5.tmp.log
Now I need a cup of coffee.
Chuck
.
--
Here In Northeast Ohio also, The Moon is Waning Gibbous (53% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Damon's iPhone.
next reply other threads:[~2018-01-08 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:11 Chuck Hallenbeck [this message]
2018-01-09 9:22 ` [Edbrowse-dev] possible Referer issue Kevin Carhart
2018-01-09 13:01 ` Chuck Hallenbeck
2018-01-09 22:58 ` Kevin Carhart
2018-01-10 2:55 ` Chuck Hallenbeck
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=alpine.DEB.2.21.1801081058410.3263@debian.pulsar.com \
--to=chuckhallenbeck@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).