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

Experimental gdb spkg #13866

Closed
vbraun opened this issue Dec 26, 2012 · 12 comments
Closed

Experimental gdb spkg #13866

vbraun opened this issue Dec 26, 2012 · 12 comments

Comments

@vbraun
Copy link
Member

vbraun commented Dec 26, 2012

I made a quick gdb spkg. If you used SAGE_DEBUG=yes to build a debug python, then the host python will most likely be unhappy: debug and normal python have a different ABI, and new gdb's link against libpython since they have significant knowledge about python internals.

http://www.stp.dias.ie/~vbraun/Sage/spkg/gdb-7.5.1.spkg

Depends on #13669

CC: @jpflori

Component: packages: experimental

Author: Volker Braun

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/13866

@vbraun
Copy link
Member Author

vbraun commented Dec 26, 2012

comment:1

Usable but still need to fill out SPKG.txt

@simon-king-jena
Copy link
Member

comment:3

What does one need to do in order to use it? With the current SAGE_DEBUG version of sage-5.6.b1 as discussed on #13864, when I simply install the gdb package, running ./sage -gdb results in

/home/simon/SAGE/debug/sage-5.6.beta1/local/bin/sage-ipython
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 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-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/simon/SAGE/debug/sage-5.6.beta1/local/bin/python...done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Python 2.7.3 (default, Dec 28 2012, 14:58:54) 
[GCC 4.6.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)

/home/simon/SAGE/debug/sage-5.6.beta1/local/lib/python2.7/site-packages/IPython/ipmaker.py in force_import(modname, force_reload)
     61         reload(sys.modules[modname])
     62     else:
---> 63         __import__(modname)
     64         
     65 

ImportError: No module named ipy_profile_sage
Error importing ipy_profile_sage - perhaps you should run %upgrade?
WARNING: Loading of ipy_profile_sage failed.

Hence, do I need to re-install something? ./sage -ba even?

@vbraun
Copy link
Member Author

vbraun commented Dec 28, 2012

Dependencies: #13669

@vbraun
Copy link
Member Author

vbraun commented Dec 28, 2012

comment:4

You just need the fix from #13669 which I posted ages ago but nobody wants to review a one-liner so until then sage -gdb stays broken no matter what version of gdb you have.

@vbraun
Copy link
Member Author

vbraun commented Dec 28, 2012

Author: Volker Braun

@vbraun
Copy link
Member Author

vbraun commented Jan 13, 2013

comment:5

I've filled in the SPKG.txt so this is ready to become an experimental spkg

@jdemeyer
Copy link

comment:6

Nitpicks: remove spkg-install~ and probably you should remove the corresponding entry from `.hgignore.

Are you sure that gmp, mpfr, mpc and ppl are dependencies of gdb? I don't really find any evidence of that. I agree that PPL is checked for, but it doesn't seem required:

checking for version 0.11 (revision 0 or later) of PPL... no

@vbraun
Copy link
Member Author

vbraun commented Jan 14, 2013

comment:7

I removed the backup~ file.

I don't know what gdb uses gmp, mpfr, mpc, ppl for, but the configure script lets you specify them. GDB doesn't link against these libraries but perhaps it picks bitwidths from headers? In any case since we do ship with all of them I thought it best to add them to configure.

@jdemeyer
Copy link

comment:8

Replying to @vbraun:

I don't know what gdb uses gmp, mpfr, mpc, ppl for, but the configure script lets you specify them.

Yes, that's weird. It looks like they copy/pasted the GCC configure script. I agree that it doesn't hurt.

@vbraun
Copy link
Member Author

vbraun commented Jan 15, 2013

comment:9

For the record, this spkg can't work on OSX because of Apple braindamage:

(sage-sh) vbraun@bsd:sage-5.4.rc1$ gdb python
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 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-apple-darwin10.8.0".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /Users/vbraun/sage-5.4.rc1/local/bin/python...
warning: `/Users/vbraun/sage-5.4.rc1/spkg/build/python-2.7.3.p0/src/Modules/python.o': can't open to read symbols: No such file or directory.
(no debugging symbols found)...done.
(gdb) run
Starting program: /Users/vbraun/sage-5.4.rc1/local/bin/python 
Unable to find Mach task port for process-id 27416: (os/kern) failure (0x5).
 (please check gdb is codesigned - see taskgated(8))

@jdemeyer
Copy link

Reviewer: Jeroen Demeyer

@haraldschilly
Copy link
Member

comment:11

spkg has been mirrored.

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

No branches or pull requests

4 participants