Opened 14 years ago

Closed 12 years ago

#24492 closed defect (fixed)

bzr 2.1.0 produces a 'bus error' on status and push operations.

Reported by: markblackman Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc:
Port: bzr

Description (last modified by jmroot (Joshua Root))

perform a 'bzr status' on a directory with a .bzr repository.

A python issue at heart?

get 'Bus Error' and following apple crash dump.

Attachments (2)

bzr_bus_error.txt (16.4 KB) - added by markblackman 14 years ago.
bus error full text with formatting intact
bzr_segfault.txt (16.2 KB) - added by markblackman 14 years ago.

Download all attachments as: .zip

Change History (9)

Changed 14 years ago by markblackman

Attachment: bzr_bus_error.txt added

bus error full text with formatting intact

comment:1 Changed 14 years ago by jmroot (Joshua Root)

Description: modified (diff)
Owner: changed from macports-tickets@… to raimue@…

Please remember to cc the maintainer. You can use WikiFormatting to display pre-formatted text correctly, but something this large is better as an attachment anyway.

comment:2 Changed 14 years ago by raimue (Rainer Müller)

Hm, you have Snow Leopard on an i386 only Mac. Did you recently migrate to Snow Leopard without rebuilding your ports?

comment:3 in reply to:  2 Changed 14 years ago by markblackman

Replying to raimue@…:

Hm, you have Snow Leopard on an i386 only Mac. Did you recently migrate to Snow Leopard without rebuilding your ports?

I think I rebuilt them on the computer in question. To be honest, I can't really recall as I'm responsible for about 4 computers and I know I have done the full reinstall on other machines, but not sure about this one.

What's a simple test to confirm that hypothesis?

comment:4 Changed 14 years ago by markblackman

So to test that hypothesis, I removed all of the original macports installation and rebuilt bzr and python etc from scratch.

I now get a segmentation fault on 'bzr status' in a directory with a pre-existing repository.

attaching the segmentation fault trace

Changed 14 years ago by markblackman

Attachment: bzr_segfault.txt added

comment:5 Changed 14 years ago by raimue (Rainer Müller)

Unfortunately I am unable to reproduce this.

As a workaround, you should be able to get a working bzr again if you remove the file /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/bzrlib/_dirstate_helpers_pyx.so and add ignore_missing_extensions=True to your bazaar.conf as described in the bzr FAQ.

Either this is specific to 32-bit Snow Leopard (for which you would be the only one seeing this) or there is something in your configuration causing these problems.

comment:6 Changed 13 years ago by jmroot (Joshua Root)

Is this still a problem with 2.3.1?

comment:7 Changed 12 years ago by raimue (Rainer Müller)

Resolution: fixed
Status: newclosed

I still can't reproduce this. bzr uses python27 now, so this could have been fixed in between.

Note: See TracTickets for help on using tickets.