Re: Serious GORM bug

[Jamie Ramone]

I'm not sure how much more details you need. I stated that dragging a connection to any of the objects in the document window (i.e. the main project window) caused a segfault. I later discovered that dragging from these objects toward any other one, outside that window, worked OK. And it seems to be present in the current version of Gorm and updating the GNUstep libs didn't alleviate the problem, which says to me that it's Gorm-specific. Oh and the GDB backtrace is from the old code. Would it help to make another one with the new code? If so just let me know and I'll produce one.

On Sun, Dec 29, 2013 at 6:20 PM, Fred Kiefer <address@hidden> wrote:

On 29.12.2013 21:58, Gregory Casamento wrote:
> Between windows or between applications.  I believe you’re hitting
> the same bug Fred may be hitting, I’m working on a potential fix
> now.

You might be wrong here. German's bug, that I investigated, was Gorm
specific. If you advice Jamie to drag between another application and
GWorkspace it may never trigger the same bug. It might trigger a similar
bug in GWorkspace if it has similar code to Gorm, but how likely is that?

And I wasn't able to reproduce Jamie's bug with Gorm. But then he never
gave enough details to be sure.

As you may remember German's bug did not include a segmentation fault,
which is the symptom Jamie is getting. What I would like to see is a
stack trace from Jamie with the current GNUstep code. With his old one I
was never sure whether I was looking at the same line of code. For me
NSWindow.m:4288 is in the middle of the GSPerformVoidDragSelector macro,
which isn't very likely.

I really would like to establish the facts before coming to conclusions
about the nature of the bug.

Fred

_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev