Processed: Re: Bug#378721: vim-lesstif: gvim always crashes during startup
Processing commands for [EMAIL PROTECTED]: > unblock 378721 by 379011 Bug#378721: vim-lesstif: gvim always crashes during startup Was blocked by: 379011 Blocking bugs of 378721 removed: 379011 > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
unblock 378721 by 379011 thanks On Sun, Aug 27, 2006 at 03:41:35AM +0100, Ben Hutchings wrote: > XmEnhancedButton doesn't initially have an XmPrimitiveClassExtRec of its > own (primitive_class.extension is NULL) so I'm not sure how it gets one. > Using a copy of the record from XmPushButton works around the bug in > vim: Thanks for the patch. I'm currently building Vim to verify the fix. If that's successful, we'll probably upload in the next couple days. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
On Thu, Jul 27, 2006 at 07:32:10PM +0400, Andrey Kiselev wrote: > I have created the bugreport in the lesstif Bugzilla: > > > http://sourceforge.net/tracker/index.php?func=detail&aid=1529729&group_id=8596&atid=108596 Thanks. > So this bug probably could be reassigned to lesstif package. It has already been cloned to lesstif2 as #379011. You may wish to point that out in the Sf bug since 379011 contains a full backtrace. I'm keeping this bug open (and blocked by 379011) so other people seeing the same problem will (hopefully) see the bug. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
I have created the bugreport in the lesstif Bugzilla: http://sourceforge.net/tracker/index.php?func=detail&aid=1529729&group_id=8596&atid=108596 So this bug probably could be reassigned to lesstif package. Best regards, Andrey -- Andrey V. Kiselev ICQ# 26871517 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
On Mon, Jul 24, 2006 at 12:25:04PM -0400, James Vega wrote: > > > This was reported a week or so ago on the vim-dev mailing list, > > > too. It seems that using lesstiff-dev/lesstiff1 also works well. > > > > I have tried the lesstiff-dev/lesstiff1 without success. Can't build vim > > with it... > > I built Vim fine with that. Simply changing the lesstif2-dev > Build-Depends to lesstif-dev and rebuilding provided a package that I > was able to use. Ooops... Now I did it too successfully! > I'm not sure what the functional differences between lesstif1 and > lesstif2 are, though. The only wisible thing (for the moment) is a problem with toolbar rendering. With toolbar switched off gvim seems to work fine. I will use it and report here if there will be any important problem with such a build. From my user's point of view that minor disfunction is much better than completely unusable software! > I'd rather lesstif2 be fixed or have someone knowledgeable about > lesstif1/lesstif2 let us know whether there will be any drawbacks if > we were to switch to lesstif1. I will try to create the bugreport for lesstif upstream as soon as I will have a bit of free time. Regards, Andrey -- Andrey V. Kiselev ICQ# 26871517 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
On Mon, Jul 24, 2006 at 04:28:06PM +0400, Andrey Kiselev wrote: > On Wed, Jul 19, 2006 at 09:32:00AM -0400, James Vega wrote: > > > In addition I have built vim package using libmotif from unstable > > > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > > > lesstif, but it renders vim-lesstif completely unusable. > > > > This was reported a week or so ago on the vim-dev mailing list, too. It > > seems that using lesstiff-dev/lesstiff1 also works well. > > I have tried the lesstiff-dev/lesstiff1 without success. Can't build vim > with it... I built Vim fine with that. Simply changing the lesstif2-dev Build-Depends to lesstif-dev and rebuilding provided a package that I was able to use. I'm not sure what the functional differences between lesstif1 and lesstif2 are, though. I'd rather lesstif2 be fixed or have someone knowledgeable about lesstif1/lesstif2 let us know whether there will be any drawbacks if we were to switch to lesstif1. > > I don't see a problem with switching to that or libmotif to build our > > Vim package. > > libmotif is non-free and not available in testing, so it is probably not > the best solution. Agreed. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
On Wed, Jul 19, 2006 at 01:53:54PM +0200, Stefano Zacchiroli wrote: > > In addition I have built vim package using libmotif from unstable > > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > > lesstif, but it renders vim-lesstif completely unusable. > > Could you please compare the versions of lesstif against which yours > (fixed) binary works and ours (broken) binary does not? I built the package using Motif, not lesstif. The package does not work with lesstif 0.94.4-2 from testing and with 0.95.0 from upstream. Works with libmotif 2.2.3-1.4 from unstable. Regards, Andrey -- Andrey V. Kiselev ICQ# 26871517 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
On Wed, Jul 19, 2006 at 09:32:00AM -0400, James Vega wrote: > > In addition I have built vim package using libmotif from unstable > > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > > lesstif, but it renders vim-lesstif completely unusable. > > This was reported a week or so ago on the vim-dev mailing list, too. It > seems that using lesstiff-dev/lesstiff1 also works well. I have tried the lesstiff-dev/lesstiff1 without success. Can't build vim with it... > I don't see a problem with switching to that or libmotif to build our > Vim package. libmotif is non-free and not available in testing, so it is probably not the best solution. Best regards, Andrey -- Andrey V. Kiselev ICQ# 26871517 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
clone 378721 -1 reassign -1 lesstif2 0.94.4-2 retitle -1 lesstif2 causes segfault when launching gvim block 378721 by -1 thanks On Wed, Jul 19, 2006 at 09:32:00AM -0400, James Vega wrote: > On Wed, Jul 19, 2006 at 02:48:25PM +0400, Andrey Kiselev wrote: > > On Tue, Jul 18, 2006 at 06:44:29PM +0400, Andrey Kiselev wrote: > > > Lesstif variant of gvim does not work on my system and crashes during > > > startup. There is backtrace log from the gdb: > > > > In addition I have built vim package using libmotif from unstable > > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > > lesstif, but it renders vim-lesstif completely unusable. > > This was reported a week or so ago on the vim-dev mailing list, too. It > seems that using lesstiff-dev/lesstiff1 also works well. I don't see a > problem with switching to that or libmotif to build our Vim package. > > We should probably clone this bug for lesstiff2 though. I'm going to > take a look at the crash with debug packages installed and see if I can > narrow down the problem. Vim built against libmotif or lesstif1 works fine so it appears to be an issue in lesstif2. Here's a full backtrace: (gdb) run -g Starting program: /usr/bin/vim.lesstif -g Program received signal SIGSEGV, Segmentation fault. 0(gdb) bt full #0 0x4741545f in ?? () No symbol table info available. #1 0xb7eacaec in XmWidgetGetBaselines (w=0x8308218, baselines=0xbfe754b8, line_count=0xbfe754b4) at ../../../lib/Xm-2.1/Primitive.c:1468 No locals. #2 0xb7ebe4d7 in constraint_set_values (current=0xbfe758a0, request=0xbfe75580, new_w=0x8308218, args=0x83086d0, num_args=0xbfe75518) at ../../../lib/Xm-2.1/RowColumn.c:3030 savew = (Widget) 0xb7ba747c pos = baselines = num_baselines = i = rc = (Widget) 0x82f7650 #3 0xb7b89cae in CallConstraintSetValues (class=0xb7f3fc40, current=0xbfe758a0, request=0xbfe75580, new=0x8308218, args=0x83086d0, num_args=1) at ../../src/SetValues.c:165 redisplay = 0 '\0' set_values = (XtSetValuesFunc) 0xb7ebe2f0 superclass = #4 0xb7b8a49b in XtSetValues (w=0x8308218, args=0x83086d0, num_args=1) at ../../src/SetValues.c:263 call_data = {type = 0xbfe75d68 "{\235¸·ÌFº·Ô]ç¿", widget = 0xbfe75d64, request = 0x0, reply = 0x1, result = 137397968} oldw = (Widget) 0x8308218 reqw = (Widget) 0x0 oldwCache = {1.5250282549293968e-269, 3.6796085506835599e-311, 0, 1.5906990497342008e-314, 7.2911220215723421e-304, 3.1259612305775811e-269, 3.0922951699427225e-269, 0, 0, 9.8813129168249309e-324, 3.0054262358678347e-269, 6.7971271789705357e-313, 5.0927898983166536e-313, 4.2503627698937639e-314, 1.2697487098120036e-321, 2.9521880136714606e-304, 1.820546087458726e-306, 2.1219957919534036e-314, 4.2439915819305446e-314, 0, 1.2648080533535912e-321, 2.9619283183614458e-269, 6.7847181420208009e-316, 5.411089266961e-312, 6.7883307500231921e-316, 3.1269779160500675e-269, 5.4747491406904026e-312, 6.7883267974980254e-316, 0, 4.9406564584124654e-324, 2.9813723818483117e-269, 4.1720778230812489e-309, 4.2093997773157533e-318, 1.3906711615670009e-309, 1.684284215785749e-305, 9.8813129168249309e-324, 0, 4.2439915819305446e-314, 3.0404211043384278e-269, 2.1219957909652723e-314, 0, 1.515646974598114e-269, 4.2439915819305446e-314, 5.0927898984154667e-313, 1.8666091202133461e-301, 1.8666251506862665e-301, 1.2433593296903789e-316, -4.0625372208568348e-41, -3.5882489812986341e-40, -4.0783318623078515e-41, 1.8666215801380385e-301, -4.0783303624415934e-41, 3.1336095698570056e-269, -4.0647086852709505e-41, ---Type to continue, or q to quit--- 7.2911222404310979e-304, 2.0231988197199046e-320, 4.2439915819305446e-314, 0, 4.2439915977406453e-314, 3.7054923438093491e-322, 2.4721250971148513e-311, -3.0368870253929505e-40, 3.1267951370545184e-269, 1.5285154609927735e-312, -3.0216479045929189e-40, 2.0231988197199046e-320, 4.2507272774958013e-313, -3.6013541309811072e-40, 2.9775298029166379e-313, 8.4383645542068199e-318, 3.1267951379796377e-269, -5.6901967341587578e-40, 1.5214390223830445e-314, -3.4349919772964845e-40, 1.8666216366819618e-301, -3.4347122122040505e-40, 1.523396640905198e-314, -3.5967175846873703e-40, 2.8482404453057754e-306, -0.7299140538739266, -3.3301064845359842e-40, 3.6447789629096704e-314, -2.482202955223e-40, -2.5068617337691947e-40, 4.6086794030583438e-313, -3.3287227007530825e-40, 7.2087959780302468e-312, 0, 4.608448868322502e-313, -5.73368143100035e-40, -0.73000752907944788, -0.72999797754661422, 1.4256886820418483e-313, 2.1219957909652723e-314, 2.1219957909652723e-314, -0.73001323633567672, 2.06228741933143e-313, -0.72997093200683594, 2.1219957909652723e-314, -0.73002660256578356} reqwCache = {1.5250282549293968e-269, 3.6796085506835599e-311, 0, 1.5906989706836975e-314, 7.2911220215723421e-304, 3.1259612305775811e-269, 3
Processed: Re: Bug#378721: vim-lesstif: gvim always crashes during startup
Processing commands for [EMAIL PROTECTED]: > clone 378721 -1 Bug#378721: vim-lesstif: gvim always crashes during startup Bug 378721 cloned as bug 379011. > reassign -1 lesstif2 0.94.4-2 Bug#379011: vim-lesstif: gvim always crashes during startup Bug reassigned from package `vim-lesstif' to `lesstif2'. > retitle -1 lesstif2 causes segfault when launching gvim Bug#379011: vim-lesstif: gvim always crashes during startup Changed Bug title. > block 378721 by -1 Bug#378721: vim-lesstif: gvim always crashes during startup Was not blocked by any bugs. Blocking bugs of 378721 added: -1 > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
On Wed, Jul 19, 2006 at 01:53:54PM +0200, Stefano Zacchiroli wrote: > On Wed, Jul 19, 2006 at 02:48:25PM +0400, Andrey Kiselev wrote: > > > Lesstif variant of gvim does not work on my system and crashes during > > > startup. There is backtrace log from the gdb: > > In addition I have built vim package using libmotif from unstable > > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > > lesstif, but it renders vim-lesstif completely unusable. > > Could you please compare the versions of lesstif against which yours > (fixed) binary works and ours (broken) binary does not? He compiled against libmotif3, which is in non-free. I don't consider that an option for us. I'll check whether using lesstif1/lesstif-dev works. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
On Wed, Jul 19, 2006 at 02:48:25PM +0400, Andrey Kiselev wrote: > On Tue, Jul 18, 2006 at 06:44:29PM +0400, Andrey Kiselev wrote: > > Lesstif variant of gvim does not work on my system and crashes during > > startup. There is backtrace log from the gdb: > > In addition I have built vim package using libmotif from unstable > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > lesstif, but it renders vim-lesstif completely unusable. This was reported a week or so ago on the vim-dev mailing list, too. It seems that using lesstiff-dev/lesstiff1 also works well. I don't see a problem with switching to that or libmotif to build our Vim package. We should probably clone this bug for lesstiff2 though. I'm going to take a look at the crash with debug packages installed and see if I can narrow down the problem. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
On Wed, Jul 19, 2006 at 02:48:25PM +0400, Andrey Kiselev wrote: > > Lesstif variant of gvim does not work on my system and crashes during > > startup. There is backtrace log from the gdb: > In addition I have built vim package using libmotif from unstable > (2.2.3-1.4) and it works just fine. So it is most likely a problem with > lesstif, but it renders vim-lesstif completely unusable. Could you please compare the versions of lesstif against which yours (fixed) binary works and ours (broken) binary does not? It would be a lot helpful ... Many thanks in advance, Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Bug#378721: vim-lesstif: gvim always crashes during startup
On Tue, Jul 18, 2006 at 06:44:29PM +0400, Andrey Kiselev wrote: > Lesstif variant of gvim does not work on my system and crashes during > startup. There is backtrace log from the gdb: In addition I have built vim package using libmotif from unstable (2.2.3-1.4) and it works just fine. So it is most likely a problem with lesstif, but it renders vim-lesstif completely unusable. Regards, Andrey -- Andrey V. Kiselev ICQ# 26871517 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378721: vim-lesstif: gvim always crashes during startup
Package: vim-lesstif Version: 1:7.0-035+1 Severity: grave Justification: renders package unusable Lesstif variant of gvim does not work on my system and crashes during startup. There is backtrace log from the gdb: Program received signal SIGSEGV, Segmentation fault. 0x545c in ?? () (gdb) bt #0 0x545c in ?? () #1 0xb7e21491 in XmWidgetGetBaselines () from /lib/libXm.so.2 #2 0xb7e364ac in XmOptionLabelGadget () from /lib/libXm.so.2 #3 0xb7b08cae in XtSetSensitive () from /usr/lib/libXt.so.6 #4 0xb7b0949b in XtSetValues () from /usr/lib/libXt.so.6 #5 0xb7b1c05c in XtVaSetValues () from /usr/lib/libXt.so.6 #6 0x0819b4b7 in ?? () #7 0x082db6c0 in ?? () #8 0x081d5895 in _XmStrings () #9 0x082dbe48 in ?? () #10 0x in ?? () I am not sure that it is vim-lesstif problem, it is likely a bug in the lesstif library, but it seriously affects vim, so I decided to report the vim bug. I have tried to rebuild the vim from sources with the latest lesstif library (0.95.0) and got exactly the same problem. I am wondering does someone have the same results with vim-lesstif, or it is just my local problem? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages vim-lesstif depends on: ii lesstif2 1:0.94.4-2 OSF/Motif 2.1 implementation relea ii libacl1 2.2.39-1Access control list shared library ii libc62.3.6-15GNU C Library: Shared libraries ii libgpmg1 1.19.6-22 General Purpose Mouse - shared lib ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libncurses5 5.5-2 Shared libraries for terminal hand ii libsm6 1:1.0.0-4 X11 Session Management library ii libx11-6 2:1.0.0-7 X11 client-side library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxmu6 1:1.0.1-3 X11 miscellaneous utility library ii libxt6 1:1.0.0-5 X11 toolkit intrinsics library ii vim-common 1:7.0-035+1 Vi IMproved - Common files ii vim-gui-common 1:7.0-035+1 Vi IMproved - Common GUI files ii vim-runtime 1:7.0-035+1 Vi IMproved - Runtime files vim-lesstif recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]