Bug#303551: Help with inkscape bug #303551
Hi alltogether! In bug #303551 it was reported that inkscape segfaults on startup. strace output and a core file are attached to the bugreport. ltrace outputs nothing and never finishes. gdb however gives > [EMAIL PROTECTED]:/tmp $ gdb -c inkscape_ppc_segfault.core > /usr/bin/inkscape > GNU gdb 6.3-debian > [...snip...] > Core was generated by `inkscape'. > Program terminated with signal 11, Segmentation fault. > #0 ?0x30009da0 in ?? () > (gdb) bt > #0 ?0x30009da0 in ?? () > #1 ?0x30009e7c in ?? () > Previous frame identical to this frame (corrupt stack?) I can't reproduce this here on my PB, neither Guido Günther could. We first thought that prelink could be the culprit, but this doesn't seem to be the case. So far it seems to be a problem unique to the submitter's setup but we don't know were to look at. Can someone on this list reproduce this bug or has an idea how to debug this? Thank you very much, Wolfi signature.asc Description: Digital signature
Bug#303551: Help with inkscape bug #303551
On Wed, May 11, 2005 at 09:16:02PM +0200, Wolfram Quester wrote: > > Hi alltogether! > > > In bug #303551 it was reported that inkscape segfaults on startup. > strace output and a core file are attached to the bugreport. ltrace > outputs nothing and never finishes. gdb however gives > > > [EMAIL PROTECTED]:/tmp $ gdb -c inkscape_ppc_segfault.core > > /usr/bin/inkscape > > GNU gdb 6.3-debian > > [...snip...] > > Core was generated by `inkscape'. > > Program terminated with signal 11, Segmentation fault. > > #0 ?0x30009da0 in ?? () > > (gdb) bt > > #0 ?0x30009da0 in ?? () > > #1 ?0x30009e7c in ?? () > > Previous frame identical to this frame (corrupt stack?) > > I can't reproduce this here on my PB, neither Guido Günther could. > We first thought that prelink could be the culprit, but this doesn't > seem to be the case. So far it seems to be a problem unique to the > submitter's setup but we don't know were to look at. > > Can someone on this list reproduce this bug or has an idea how to debug > this? I just recently used inkscape an my ibook for some artwork and didn't see a single crash. I do also not remember any crashes at startup on my previously used Pismo. Uwe -- MMK GmbH, Universitaetsstr. 11, 58097 Hagen [EMAIL PROTECTED] Tel: +2331 840446Fax: +2331 843920 signature.asc Description: Digital signature
Bug#303551: Help with inkscape bug #303551
On Thursday 12 May 2005 04:30, Michel DÃnzer wrote: > On Wed, 2005-05-11 at 21:16 +0200, Wolfram Quester wrote: > > In bug #303551 it was reported that inkscape segfaults on startup. > > strace output and a core file are attached to the bugreport. ltrace > > outputs nothing and never finishes. gdb however gives > > or has an idea how to debug this? > > I recently encountered similarly mysterious crashes in some > applications. None of my debugging attempts seemed to make much sense, > so I ended up going through all the dependencies and reinstalling them > one at a time. Lo and behold, the crashes vanished after reinstalling > one of the library packages. So apparently the library had somehow got > corrupted on the filesystem. > > No idea if this is a similar issue, but it's definitely something worth > trying I think. Yes, it seems to have been similar. Made a little script that reinstalled each dependency, then tried to launch inkscape. After a while of running in the background, inkscape popped up, and the output was: Setting up libgtkmm-2.4-1 (2.4.11-1) ... libgtkmm-2.4-1 fixed it :) I'm still not sure what the problem was, but I guess it's been fixed now, whatever it was :) Thanks Michel, Wolfram, and Guido :) -- Lee. Please send replies to the list, not to my email address.
Bug#303551: Help with inkscape bug #303551
Hi Lee, hi Michel, On Thu, May 12, 2005 at 10:32:06AM +0100, Lee Braiden wrote: > On Thursday 12 May 2005 04:30, Michel Dänzer wrote: > > On Wed, 2005-05-11 at 21:16 +0200, Wolfram Quester wrote: > > > In bug #303551 it was reported that inkscape segfaults on startup. > > > strace output and a core file are attached to the bugreport. ltrace > > > outputs nothing and never finishes. gdb however gives > > > or has an idea how to debug this? > > > > I recently encountered similarly mysterious crashes in some > > applications. None of my debugging attempts seemed to make much sense, > > so I ended up going through all the dependencies and reinstalling them > > one at a time. Lo and behold, the crashes vanished after reinstalling > > one of the library packages. So apparently the library had somehow got > > corrupted on the filesystem. > > > > No idea if this is a similar issue, but it's definitely something worth > > trying I think. > > Yes, it seems to have been similar. Made a little script that reinstalled > each dependency, then tried to launch inkscape. After a while of running in > the background, inkscape popped up, and the output was: > > Setting up libgtkmm-2.4-1 (2.4.11-1) ... > libgtkmm-2.4-1 fixed it > > :) > > I'm still not sure what the problem was, but I guess it's been fixed now, > whatever it was :) It's nice to know it works for you now. I'll close the bug then and I hope you have fun with inkscape ;-) Thanks to all who tried to help. With best wishes, Wolfi > > Thanks Michel, Wolfram, and Guido :) > > -- > Lee. > > Please send replies to the list, not to my email address. signature.asc Description: Digital signature
Bug#303551: Help with inkscape bug #303551
On Thu, May 12, 2005 at 02:24:40PM +0200, Wolfram Quester wrote: > Hi Lee, hi Michel, > > On Thu, May 12, 2005 at 10:32:06AM +0100, Lee Braiden wrote: > > On Thursday 12 May 2005 04:30, Michel Dänzer wrote: > > > On Wed, 2005-05-11 at 21:16 +0200, Wolfram Quester wrote: > > > > In bug #303551 it was reported that inkscape segfaults on startup. > > > > strace output and a core file are attached to the bugreport. ltrace > > > > outputs nothing and never finishes. gdb however gives > > > > or has an idea how to debug this? > > > > > > I recently encountered similarly mysterious crashes in some > > > applications. None of my debugging attempts seemed to make much sense, > > > so I ended up going through all the dependencies and reinstalling them > > > one at a time. Lo and behold, the crashes vanished after reinstalling > > > one of the library packages. So apparently the library had somehow got > > > corrupted on the filesystem. > > > > > > No idea if this is a similar issue, but it's definitely something worth > > > trying I think. > > > > Yes, it seems to have been similar. Made a little script that reinstalled > > each dependency, then tried to launch inkscape. After a while of running > > in > > the background, inkscape popped up, and the output was: > > > > Setting up libgtkmm-2.4-1 (2.4.11-1) ... > > libgtkmm-2.4-1 fixed it > > > > :) > > > > I'm still not sure what the problem was, but I guess it's been fixed now, > > whatever it was :) > > It's nice to know it works for you now. I'll close the bug then and I > hope you have fun with inkscape ;-) Since several people are seeing this there seems to be still a bug somewhere, maybe in unprelinking? Now that we now the library that had the problem, it would be nice to see what a prelink/unprelink cycle of that library shows. Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
