Entered into Bugzilla: http://bugs.winehq.org/show_bug.cgi?id=2544 On Wed, 27 Oct 2004 13:55:02 -0700, Mark Knecht <markknecht@xxxxxxxxx> wrote: > Found it!! > > http://www.winehq.org/hypermail/wine-cvs/2004/05/0228.html > > I thik this probably makes sense. The linux app (jack_fst) is what I > think the developers call a 'libwine' application. It looks like this > edit has something to do with that. However, this edit was actually > responsible for the almost total recomilation of Wine so who knows... > > Now, how does one go about looking at the changes? Or is that where I > should start? The very end of chapter 18 suggests reporting this to > Bugzilla, so I'll do that, and also possibly getting on the wine-dev > mailing list. Would that possibly result in a fast response? > > since this is a Linux program that's segfaulting it's possible that > the right fix is in that program and not Wine at all, but being that I > don't program we're pretty quickly going to get to the end of my > usefulness. (Well, possibly I can still learn and contribute a bit...) > > > > Thanks, > Mark > > On Wed, 27 Oct 2004 12:42:36 -0700, Mark Knecht <markknecht@xxxxxxxxx> wrote: > > Got it. Very helpful. Thanks! Getting started now. > > > > Back in an hour or two... > > > > Thanks, > > Mark > > > > > > > > > > On Wed, 27 Oct 2004 12:34:01 -0700, Duane Clark <dclark@xxxxxxxxxxx> wrote: > > > Mark Knecht wrote: > > > > ... > > > > cvs update -PAd -D "2004-05-25 CDT" > > > > > > > > (Build takes 8 minutes. PROGRAM FAILS!) > > > > > > > > SEGFAULT > > > > > > > > Amazing. 0505 worked. 0615 failed. 0525 was the exact middle. I did > > > > that first. It failed. I then jumped to 0515 (middle of 0505 and 0525) > > > > and had to work my way up. Too bad I didn't try 0524 last night... ;-) > > > > > > > > Now, this is a Linux program that's crashing. We have the source, and > > > > the program is relatively small. Does my command above include the > > > > changes made on the 25th according to the change log, or does it only > > > > include changes up through the 24th????? > > > > > > It only includes changes through the end of the day (midnight) of the 24th. > > > > > > > > > > > How do I get down to udnerstand which *file* causes my problem? > > > > > > > > > > First go to http://www.winehq.org/hypermail/wine-cvs/2004/05/index.html > > > > > > There were only a few files committed on the 25th, so I would do them > > > one at a time. Pick a time between the commit times of the first two: > > > > > > cvs update -PAd -D "2004-05-25 00:09:00CDT" > > > > > > It is useful to watch as the files are patched, and make sure that only > > > the files expected to be updated are patched. In this case, the only > > > file that should have been patched is dlls/kernel/kernel_main.c Compile > > > and try. If that works, try the next commit. > > > > > > _______________________________________________ > > > > > > > > > wine-users mailing list > > > wine-users@xxxxxxxxxx > > > http://www.winehq.org/mailman/listinfo/wine-users > > > > > > _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
