[tex-live] extractbb/ebb/xbb and also Mac OS X

[George N. White III]

On linux (fedora 8, i686)

$ which extractbb
/usr/local/texlive/2008/bin/i386-linux/extractbb
$ cp  /usr/local/texlive/2008/texmf-dist/doc/metapost/featpost/png/myicon.png .
$ extractbb -v -m myicon.png
Writing to ./myicon.bb: Bounding box: 0 0 52 26
$ cat myicon.bb
%%Title: ./myicon.png
%%Creator: extractbb Version 0.2
%%BoundingBox: 0 0 52 26
%%CreationDate: Sun Sep 14 13:05:39 2008

So, it may require that the options be given separately.  However,
extractbb aborts after writing a .xbb:

$ extractbb -v myicon.png
Writing to ./myicon.xbb: Bounding box: 0 0 72 36
*** glibc detected *** extractbb: free(): invalid next size (fast):
0x09cadab8 ***
======= Backtrace: =========
/lib/libc.so.6[0x98aac1]
/lib/libc.so.6(cfree+0x90)[0x98e0f0]
extractbb[0x80b1b43]
extractbb[0x80b21eb]
extractbb[0x80b2886]
extractbb[0x80655b9]
/lib/libc.so.6(__libc_start_main+0xe0)[0x937390]
extractbb[0x80496a1]
======= Memory map: ========
00110000-00111000 r-xp 00110000 00:00 0          [vdso]
0070f000-0071a000 r-xp 00000000 fd:00 15533592
/lib/libgcc_s-4.1.2-20070925.so.1
0071a000-0071b000 rw-p 0000a000 fd:00 15533592
/lib/libgcc_s-4.1.2-20070925.so.1
00902000-0091d000 r-xp 00000000 fd:00 15532308   /lib/ld-2.7.so
0091d000-0091e000 r--p 0001a000 fd:00 15532308   /lib/ld-2.7.so
0091e000-0091f000 rw-p 0001b000 fd:00 15532308   /lib/ld-2.7.so
00921000-00a74000 r-xp 00000000 fd:00 15532426   /lib/libc-2.7.so
00a74000-00a76000 r--p 00153000 fd:00 15532426   /lib/libc-2.7.so
00a76000-00a77000 rw-p 00155000 fd:00 15532426   /lib/libc-2.7.so
00a77000-00a7a000 rw-p 00a77000 00:00 0
00a7c000-00aa3000 r-xp 00000000 fd:00 15533549   /lib/libm-2.7.so
00aa3000-00aa4000 r--p 00026000 fd:00 15533549   /lib/libm-2.7.so
00aa4000-00aa5000 rw-p 00027000 fd:00 15533549   /lib/libm-2.7.so
08048000-080f6000 r-xp 00000000 fd:02 32835333
/Data/opt/tex/texlive/2008/bin/i386-linux/dvipdfmx
080f6000-080fb000 rw-p 000ae000 fd:02 32835333
/Data/opt/tex/texlive/2008/bin/i386-linux/dvipdfmx
080fb000-0811c000 rw-p 080fb000 00:00 0
09c77000-09eee000 rw-p 09c77000 00:00 0          [heap]
b7e00000-b7e21000 rw-p b7e00000 00:00 0
b7e21000-b7f00000 ---p b7e21000 00:00 0
b7f12000-b7f16000 rw-p b7f12000 00:00 0
bfb00000-bfb16000 rw-p bffea000 00:00 0          [stack]
Aborted

$ cat myicon.xbb
%%Title: ./myicon.png
%%Creator: extractbb Version 0.2
%%BoundingBox: 0 0 72 36
%%CreationDate: Sun Sep 14 12:59:23 2008


On Sat, Sep 13, 2008 at 8:21 PM, Peter Dyballa <Peter_Dyballa at freenet.de> wrote:
> Hello!
>
> Extractbb can work verbosely (-v), which means it echos to stdout what it
> writes to the file. And it has two modes (besides a binary one) to record
> information:
>
>        -m      Output .bb  file used in DVIPDFM
>        -x      Output .xbb file used in DVIPDFMx (default)
>
> The command 'extractbb -vm playground.jpg' provokes the message:
>
>        Writing to ./playground.xbb: Bounding box: 0 0 85 40
>
> According to the documentation a BB file should have been created. Using
> 'extractbb -vx playground.jpg' produces the correct message and the
> documented file format. 'extractbb -m playground.jpg' works as documented,
> and also 'extractbb -x playground.jpg'.
>
> When using the ebb command, the created BB file has a line
>
>        %%Creator: extractbb Version 0.2
>
> instead of
>
>        %%Creator: ebb Version ?
>
>
> The documentation and also the source code mention a command 'bbx' or 'xbb'
> which does not exist in /usr/local/texlive/2008/bin/universal-darwin (from
> middle of August, Mac TeX test distribution). Is this on purpose?


-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia