Package Details: mips-harvard-os161-gdb 7.8+os161_2.1-2

Git Clone URL: (read-only)
Package Base: mips-harvard-os161-gdb
Description: The GNU Debugger modified for mips-harvard-os161 arquitecture. This is part of toolset for the course os161 from Harvard.
Upstream URL:
Licenses: GPL, LGPL
Groups: mips-harvard-os161-toolchain
Submitter: gerito
Maintainer: gerito
Last Packager: gerito
Votes: 0
Popularity: 0.000000
First Submitted: 2017-02-13 12:47
Last Updated: 2017-07-29 08:15

Latest Comments

Anonymous comment on 2018-06-01 02:39

@sommd The error is caused because the python modules that mips-harvard-os161-gdb depend on are deleted during install.

rm -rf ${pkgdir}/usr/share/gdb

When gdb from extra isn't installed, the modules cannot load (there's a brief error). If it is installed, then the modules that load cause errors like you're seeing because they aren't compatible. I suspect that this is because gdb in extra is at version 8+ while the one in the OS/161 toolchain is still in version 7.

This quick hack to get this working is by using the --data-directory argument while running mips-harvard-os161-gdb.

$ git clone
$ cd mips-harvard-os161-git

Edit PKGBUILD so that the line I mentioned at the beginning is commented out and make sure you have mips-harvard-os161-gdb installed as is before doing the following.

$ makepkg
$ mips-harvard-os161-gdb --data-directory=/[path to where you cloned]/mips-harvard-os161-gdb/pkg/mips-harvard-os161-gdb/usr/share/gdb

Store the folder somewhere and make an alias for mips-harvard-os161-gdb so that you don't have to add it every time.

This isn't ideal but it should do until @gerito can sort out a way to fix this.

@gerito Would it be possible to install the modules in another directory that doesn't interfere with gdb from the official repos? Like /usr/share/mips-harvard-os161-gdb so that it's distinguished from /usr/share/gdb?

sommd commented on 2018-05-31 13:23

Keep getting the following error:

Traceback (most recent call last):
  File "/usr/share/gdb/python/gdb/", line 144, in auto_load_packages
  File "/usr/share/gdb/python/gdb/command/", line 756, in <module>
  File "/usr/share/gdb/python/gdb/command/", line 135, in init_env
    gdb.TYPE_CODE_RVALUE_REF : ReferenceExplorer,
AttributeError: module 'gdb' has no attribute 'TYPE_CODE_RVALUE_REF'

Which keeps printing after almost every command, making the output unreadable. The only solution I've found is to uninstall normal GDB. Any proper solutions?

Anonymous comment on 2017-07-31 17:32

@gerito Sorry for the delay! It builds perfectly fine now. Thank You.

gerito commented on 2017-07-29 08:20

I hope it works now @0xelectron, and @m51.

Please notify me for success/failure.

I wish that I could said I fixed it, but after unsuccessfully tracking the root of the problem I found a patch and I just applied.

I found another error, and I added a new dependency.

gerito commented on 2017-07-29 03:56

Sorry for the delay, I missed the first message. @m51

It takes ages for me to compile, so when I get time I will get into.

I don't know the problem, for the moment I need to create a fresh install and start from there.

I'm on it @0xelectron, and @m51.

Anonymous comment on 2017-07-27 17:23

can confirm. I've the same error as @m51. I'll too look into it.

m51 commented on 2017-04-27 10:16

the compilation of this packet fails when compiled on a 4.10.11-1-ARCH Kernel (64 bit, i5 CPU).
When compiling inside the directory "src/gdb-build/sim/mips", I have a "multiple definition of `sim_addr_range_hit_p'" error repeated some times.
Have you encountered this kind of error? In the meanwhile, I'll search for a solution.
Thank you in advance.