edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
Cc: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] Signing into my Amazon account
Date: Fri, 5 Jan 2018 21:35:32 +0100	[thread overview]
Message-ID: <20180105203532.GA30696@nautica> (raw)
In-Reply-To: <alpine.DEB.2.21.1801051434001.5756@debian.pulsar.com>

Hi Chuck,

Happy new year everyone.

Chuck Hallenbeck wrote on Fri, Jan 05, 2018:
> #1. No matter what, I always get the "Please enable
> cookies to continue"  message at the top of the sign-in page.

This is likely a js problem, some variable/field must not be set
somewhere so the text is displayed.

> #3. When I enter my sign-in info and activate the submit button,
> edbrowse segfaults.

I can reproduce this segfault, it crahes in handlerGoBrowse (in html.c)
after walking up the html tags till there is no parent anymore, and
found no handler at all, then runs the handler of the document itself
and since it is the first handler tries to get 'cf' from the null tag.

I believe we should just remove this line 1800:
                        cf = t->f0;
(I'll defer to Karl on that)


The problem is that, even after doing that, Amazon still does not log me
in after filling the information. It reloads the same page and tells me
the Email I entered is not valid, except that I think it should be, so
there must be some more javascript failing? Running with -d3 gives me a
few messages "TypeError: undefined not callable" so I am sure that
something goes wrong somewhere, but not what.

> Are there tricks I don't know about? Can others do this
> successfully? If so, how? Can I generate more helpful information
> somehow?

Reporting something that others can reproduce is already very helpful!
I have gotten the information I just gave from a tool called 'gdb'.

You need to compile edbrowse with 'make EDDEBUG=1' then running edbrowse
under gdb will give you more information about what happened during the
crash.

-- 
Dominique

  reply	other threads:[~2018-01-05 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 19:54 Chuck Hallenbeck
2018-01-05 20:35 ` Dominique Martinet [this message]
2018-01-05 20:53   ` Chuck Hallenbeck
2018-01-05 22:19     ` Kevin Carhart
2018-01-05 22:04   ` Karl Dahlke
2018-01-05 22:55     ` Kevin Carhart
2018-01-05 23:40     ` Chuck Hallenbeck
2018-01-06 12:12   ` Chuck Hallenbeck
2018-01-06 12:20     ` Dominique Martinet

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=20180105203532.GA30696@nautica \
    --to=asmadeus@codewreck.org \
    --cc=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).