From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] amazon and its JS
Date: Sat, 13 Jan 2018 10:55:45 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801131054540.1328@debian.pulsar.com> (raw)
In-Reply-To: <20180013091101.eklhad@comcast.net>
Hi Kevin, Karl, and all,
Let me try to recap my situation a bit. When I run edbrowse on my
ArchLinux OS, it does not segfault. Not even when it is run with
db5 redirected to /tmp/log. Like Kevin's experience though, it just
returns me to the login screen with minimum hint of what's wrong.
On Debian, running edbrowse without db5, it also never segfaults,
and like under Arch, does not recognize my credentials. '
Edbrowse segfaults only under Debian, and only when db5 is invoked
and redirected. I cannot run edbrowse with db5 set, unless it's also
redirected, because it's just too chatty.
I would be willing to give Karl access to my system if that would
help, except I have no access to my router to do any port-forwarding
or otherwise open it. And frankly I'm feeling my age recently and
am having difficulty extending my skills to include such things as
mastering gdb, core dumps, and the like. I'm an old dog and those
are new tricks. But I'm good at following instructions.
And I'm patient, and appreciative, and am not about to abandon edbrowse
and my text console just to access Amazon.
Chuck
--
Here too, In Northeast Ohio, The Moon is Waning Crescent (10% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Brittany's iPhone.
next prev parent reply other threads:[~2018-01-13 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 0:12 Kevin Carhart
2018-01-13 14:11 ` Karl Dahlke
2018-01-13 15:55 ` Chuck Hallenbeck [this message]
2018-01-13 16:27 ` Dominique Martinet
2018-01-13 17:12 ` Dominique Martinet
2018-01-13 22:06 ` Karl Dahlke
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.1801131054540.1328@debian.pulsar.com \
--to=chuckhallenbeck@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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).