Re: problems debugging with clang 3.2, gdb 7.6, libobjc2 SVN, and Ubuntu 13.10
On Fri, Oct 4, 2013 at 3:43 PM, Ivan Vučica wrote: > On 4. 10. 2013., at 21:50, Eric Wasylishen wrote: > >> >> 2. Printing ivars is broken. gdb seems to print self->isa when you do >> "print someivar" or "print self->someivar". lldb-3.2 prints an error asking >> you to report a bug. >> >> I configured gnustep-make with --enable-debug-by-default >> --enable-objc-nonfragile-abi, gnustep-base with --disable-mixedabi. >> >> I talked to Alex S. on Étoilé IRC and he observed the same two problems on a >> similar setup as me; Quentin also mentioned the ivar printing problem to me. >> > > I've also had similar problem with printing Objective-C variables on Ubuntu > 12.04, and whatever-gdb-ships-with-12-04. I think my install has a post-3.2 > clang SVN, possibly post-3.3. I would suspect it's an incompatibility between > libobjc2 and gdb/lldb, though it would be strange if David didn't see it. don't recall seeing any changes for gdb to support non-fragile ivars, that'd be my guess ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problems debugging with clang 3.2, gdb 7.6, libobjc2 SVN, and Ubuntu 13.10
On 4. 10. 2013., at 21:50, Eric Wasylishen wrote: > > 2. Printing ivars is broken. gdb seems to print self->isa when you do "print > someivar" or "print self->someivar". lldb-3.2 prints an error asking you to > report a bug. > > I configured gnustep-make with --enable-debug-by-default > --enable-objc-nonfragile-abi, gnustep-base with --disable-mixedabi. > > I talked to Alex S. on Étoilé IRC and he observed the same two problems on a > similar setup as me; Quentin also mentioned the ivar printing problem to me. > I've also had similar problem with printing Objective-C variables on Ubuntu 12.04, and whatever-gdb-ships-with-12-04. I think my install has a post-3.2 clang SVN, possibly post-3.3. I would suspect it's an incompatibility between libobjc2 and gdb/lldb, though it would be strange if David didn't see it. -- Ivan Vučica i...@vucica.net - http://ivan.vucica.net/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
problems debugging with clang 3.2, gdb 7.6, libobjc2 SVN, and Ubuntu 13.10
Hi, Just want to report that I got a new development environment set up, and I've observed two problems with debuggers: 1. "step" / "s" command in gdb doesn't step in to Objective-C methods; it acts like "next"/"n" and steps to the next line of code. I've verified that I'm compiling code with 'make debug=yes'. Same thing happens with gdb 7.6 or lldb-3.3. 2. Printing ivars is broken. gdb seems to print self->isa when you do "print someivar" or "print self->someivar". lldb-3.2 prints an error asking you to report a bug. I configured gnustep-make with --enable-debug-by-default --enable-objc-nonfragile-abi, gnustep-base with --disable-mixedabi. I talked to Alex S. on Étoilé IRC and he observed the same two problems on a similar setup as me; Quentin also mentioned the ivar printing problem to me. Anyone have an idea of where the actual problem lies, and possible workarounds? I have yet to try newer versions of clang, and plan to do that. Thanks, Eric ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSCursor mismatched push and pop
These bugs are still present: http://lists.gnu.org/archive/html/gnustep-dev/2013-09/msg0.html http://lists.gnu.org/archive/html/gnustep-dev/2013-09/msg00020.html Germán. El vie, 04-10-2013 a las 12:51 -0600, Germán Arias escribió: > El jue, 03-10-2013 a las 18:07 +0100, David Chisnall escribió: > > Hi, > > > > I managed to reproduce the NSCursor mismatched push / pop issue, with > > tracing enabled. The log is here: > > > > http://theravensnest.org/NSCursor.1.log > > > > I haven't yet done more than glance at it, but perhaps someone who knows > > this code better than me could gain more insight from it. The trace is > > from launching the application until exit. I exited after I was sure that > > the bug had been triggered. > > > > For each NSCursor push or pop[1], there is a stack trace. Ignore any > > functions in the trace that start .tesla or __tesla in the stack traces, > > these are artefacts of the instrumentation. > > > > David > > > > [1] Unfortunately, in this log it isn't totally clear whether the class or > > instance method is being called, so it looks like there are some duplicate > > pops that are actually -pop calling +pop. I'll improve the trace output > > and try to recreate it. > > > > -- Send from my Jacquard Loom > > > > > > Would be helpful know the events processed alongside the nscursor > events. The type and subtype of these. > > Germán. > > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSCursor mismatched push and pop
El jue, 03-10-2013 a las 18:07 +0100, David Chisnall escribió: > Hi, > > I managed to reproduce the NSCursor mismatched push / pop issue, with tracing > enabled. The log is here: > > http://theravensnest.org/NSCursor.1.log > > I haven't yet done more than glance at it, but perhaps someone who knows this > code better than me could gain more insight from it. The trace is from > launching the application until exit. I exited after I was sure that the bug > had been triggered. > > For each NSCursor push or pop[1], there is a stack trace. Ignore any > functions in the trace that start .tesla or __tesla in the stack traces, > these are artefacts of the instrumentation. > > David > > [1] Unfortunately, in this log it isn't totally clear whether the class or > instance method is being called, so it looks like there are some duplicate > pops that are actually -pop calling +pop. I'll improve the trace output and > try to recreate it. > > -- Send from my Jacquard Loom > > Would be helpful know the events processed alongside the nscursor events. The type and subtype of these. Germán. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
