Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong encoding causes pwndbg to crash #6

Open
Corb3nik opened this issue Aug 20, 2017 · 2 comments
Open

Wrong encoding causes pwndbg to crash #6

Corb3nik opened this issue Aug 20, 2017 · 2 comments

Comments

@Corb3nik
Copy link

With a fresh installation of pwnvm :

  1. Run the /home/vagrant/tools/pwndbg/setup.sh script.
  2. Remove Voltron from ~/.gdbinit
  3. Open gdb

I obtain the following error message :

➜  ~ gdb
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
******
Your encoding (ISO-8859-1) is different than UTF-8. pwndbg might not work properly.
You might try launching gdb with:
    LC_ALL=en_US.UTF-8 PYTHONIOENCODING=UTF-8 gdb
Make sure that en_US.UTF-8 is activated in /etc/locale.gen and you called locale-gen
******
Traceback (most recent call last):
  File "/home/vagrant/tools/pwndbg/gdbinit.py", line 36, in <module>
    import pwndbg # isort:skip
  File "/home/vagrant/tools/pwndbg/pwndbg/__init__.py", line 15, in <module>

Running gdb with LC_ALL=en_US.UTF-8 PYTHONIOENCODING=UTF-8 gdb fixes the issue.

Is there a reason for using ISO-8859-1 instead of UTF-8 by default? If not, I'll suggest a fix in a PR.

@dreyes15
Copy link

dreyes15 commented Nov 3, 2018

This appears to still be an issue. Is there a fix by any chance?

@Grazfather
Copy link
Contributor

Try this: #7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants