Ticket #181 (defect)
Opened 1 year ago
Last modified 10 months ago
Problem with SWIG exception handling
Status: closed (fixed)
| Reported by: | eb | Assigned to: | eb |
|---|---|---|---|
| Priority: | low | Milestone: | release-3.1.2 |
| Component: | build | Version: | 3.0svn |
| Keywords: | Cc: | ||
This works under Python 2.4, but not under Python 2.5 as found on Ubuntu 7.04.
eb@bufo:~/gr/trunk$ python Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from gnuradio import gr >>> gr.costas_loop_cc(0,0,0,0,1) terminate called after throwing an instance of 'std::invalid_argument' what(): order must be 2 or 4 Aborted (core dumped)
Checking g++ version:
eb@bufo:~/gr/trunk$ g++ --version g++ (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Can also be reproduced like this:
eb@bufo:~/gr/trunk$ python Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from gnuradio import gr >>> gr.firdes.hilbert(0) terminate called after throwing an instance of 'std::out_of_range' what(): Hilbert: Must have odd number of taps Aborted (core dumped)
Change History
08/30/07 20:08:16: Modified by eb
- summary changed from Problem with SWIG exception handling on Python 2.5 (possible compiler issue?) to Problem with SWIG exception handling.
09/05/07 14:34:28: Modified by eb
- owner changed from nobody to eb.
- status changed from new to assigned.
- milestone changed from to-be-decided to release-3.1.
10/22/07 12:44:39: Modified by jcorgan
- milestone changed from release-3.1 to release-3.1.1.
11/06/07 22:38:55: Modified by jcorgan
- milestone changed from release-3.1.1 to release-3.1.2.
01/15/08 10:35:05: Modified by eb
- priority changed from normal to high.
01/18/08 18:18:47: Modified by eb
- priority changed from high to low.
We appear to be triggering swig bug 1863647
Suggested work-around applied in [7461].
02/11/08 19:09:20: Modified by eb
- status changed from assigned to closed.
- resolution set to fixed.
We haven't heard any negative feedback, thus are closing it now.

Update: some of this stuff fails on Python 2.4 too. Must be our problem ;)