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

Correctly extract arch on platforms where architecure().name() fails #45

Merged
merged 1 commit into from Jan 24, 2014

Conversation

Projects
None yet
2 participants
@richo
Copy link
Contributor

commented Jan 14, 2014

This fixes that bug I showed you last night. groups() returns tuples, group() returns the content of the matchgroup.

I've tested this exactly nowhere. It also doesn't fix that server not starting bug, but I have a workaround so I'm probably not going to look into it.

FWIW, I get:

(gdb) r
Starting program: /home/ubuntu/butts

Breakpoint 1, 0x0000000000400548 in main ()
(gdb) voltron start
Starting voltron
(gdb) voltron update
Python Exception <type 'exceptions.AttributeError'> 'NoneType' object has no attribute 'update_clients':
Error occurred in Python command: 'NoneType' object has no attribute 'update_clients'
(gdb)

So it definitely seems like the server object just never gets init'd.

@richo

This comment has been minimized.

Copy link
Contributor Author

commented Jan 14, 2014

Oh, NVM. I think I'm just retarded. I think I'm meant to start voltron, then start the inferior right?

snare added a commit that referenced this pull request Jan 24, 2014

Merge pull request #45 from richo/bugs/match_arch
Correctly extract arch on platforms where architecure().name() fails

@snare snare merged commit d8006a4 into snare:master Jan 24, 2014

@snare

This comment has been minimized.

Copy link
Owner

commented Jan 24, 2014

Yeah, voltron first. On GDB you can voltron start in your .gdbinit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.