barcode @0.98_0 Segmentation violation

[hanche@…]

Short version:

; barcode -b 0534944043 -n -e isbn -o tt.ps
segmentation violation

The same happens with any encoding I have tried.

When I run it under gdb, I get this backtrace:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x00007fff86d5c4f0 in strlen ()
(gdb) back
#0  0x00007fff86d5c4f0 in strlen ()
#1  0x00007fff86ce70d9 in vsscanf_l ()
#2  0x00007fff86ccb978 in sscanf ()
#3  0x0000000100000fe1 in get_page_geometry ()
#4  0x0000000100001438 in main ()

I have only tried this on Lion, up-to-date OS and XCode.

From a look at the project home page at ​http://www.gnu.org/software/barcode/, I get the rather strong impression that this software is not being maintained upstream. If it cannot easily by fixed by a patch, perhaps it ought to be removed from macports altogether?

[hanche@…]

Argh, I realized I had not filled in the port field (at the very same moment I hit submit). Hopefully, someone with the appropriate privileges can fill it in. Sorry about that!

[hanche@…]

I have been asked to provide more specific version information. It was OS X 10.7.2, and XCode 4.1 (I was confused and thought I had the latest, but it appears I had downloaded the installer and forgotten to run it (duh).) I have also been asked what compiler I used; I have no idea, which surely means Ihave been using the macports defaults, right? I have not specified anything else either in macports.conf or the command line. (I have now run the 4.2.1 XCode installer and will soon update OS X, so I won't be able to test this particular configuration again, sorry.)

[ryandesign@…]

The compiler MacPorts chooses varies by Xcode version. With Xcode 4.1 you would have been using the llvm-gcc-4.2 compiler. Now that you have Xcode 4.2 you'll be using the clang compiler.

[jmr@…]

r95543