This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chaselton
Recipients chaselton, ethan.furman, freakboy3742, mpaolini, r.david.murray, refi64, tritium
Date 2015-07-25.18:32:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAHu5Prakzo5jEO3KjVmMgSwcLFoB3WsJAULukZOHbOz=Y++eBA@mail.gmail.com>
In-reply-to <446A5187-4E7F-419D-B231-C3BD6B9BEEC9@gmail.com>
Content
As soon as I build a PIE gdb I can.

And right now, running ./python -m test throws the ImportError...so I'll
need to resolve that first
On Jul 25, 2015 12:38 PM, "Ryan Gonzalez" <report@bugs.python.org> wrote:

>
> Ryan Gonzalez added the comment:
>
> So...I have *no* clue why _struct can't be found.
>
> Can you use gdb to get the segfault backtrace like you did before?
>
> On July 25, 2015 6:56:10 AM CDT, Cyd Haselton <report@bugs.python.org>
> wrote:
> >
> >Cyd Haselton added the comment:
> >
> >I assume so; I'm using whatever is pulled frommy fork of the git repo.
> >
> >I've actually run into a different error that occured when i rebuilt to
> >include readline support; when I run ./python -m test I;m getting
> >"ImportError: no module named _struct found."
> >
> >Trying to figure that one out first...
> >
> >----------
> >
> >_______________________________________
> >Python tracker <report@bugs.python.org>
> ><http://bugs.python.org/issue23496>
> >_______________________________________
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23496>
> _______________________________________
>
History
Date User Action Args
2015-07-25 18:32:18chaseltonsetrecipients: + chaselton, r.david.murray, freakboy3742, ethan.furman, refi64, mpaolini, tritium
2015-07-25 18:32:18chaseltonlinkissue23496 messages
2015-07-25 18:32:18chaseltoncreate