A little more poking with readelf reveals that we don't actually have any data in the .eh_frame that exists on karmic/lucid:
mcasadevall@dawn:/usr/lib/ure/lib$ readelf -x.eh_frame ./libgcc3_uno.so.karmic
Hex dump of section '.eh_frame': 0x0000c2c4 00000000 ....
mcasadevall@dawn:/usr/lib/ure/lib$ readelf -x.eh_frame ./libgcc3_uno.so.jaunty
Hex dump of section '.eh_frame': 0x00010fa8 10000000 00000000 017a5200 027c0e01 .........zR..|.. 0x00010fb8 1b0c0d00 10000000 18000000 ecddffff ................ 0x00010fc8 28000000 00000000 00000000 (...........
I believe this is the root cause of our exceptions failing to unwind. The next step is to determine what data is in the eh_frame specifically in jaunty.
A little more poking with readelf reveals that we don't actually have any data in the .eh_frame that exists on karmic/lucid:
mcasadevall@ dawn:/usr/ lib/ure/ lib$ readelf -x.eh_frame ./libgcc3_ uno.so. karmic
Hex dump of section '.eh_frame':
0x0000c2c4 00000000 ....
mcasadevall@ dawn:/usr/ lib/ure/ lib$ readelf -x.eh_frame ./libgcc3_ uno.so. jaunty
Hex dump of section '.eh_frame':
0x00010fa8 10000000 00000000 017a5200 027c0e01 .........zR..|..
0x00010fb8 1b0c0d00 10000000 18000000 ecddffff ................
0x00010fc8 28000000 00000000 00000000 (...........
I believe this is the root cause of our exceptions failing to unwind. The next step is to determine what data is in the eh_frame specifically in jaunty.