I cloned the sources from the git repo.

Attached is the result of `git bisect start HEAD wmaker-0.95.4`.

Thanks!


On Sun, Jun 16, 2013 at 3:25 PM, Christophe <christophe.cu...@free.fr>wrote:

> ----- Juan Giordana <juangiord...@gmail.com> a écrit :
> > Hello again,
> >
> > Attached is the debug.log.
> >
> > Thanks!
>
>
> Thanks to you for taking the time!
> I am pleased to see the experiment succeeded!
>
> Unfortunately, there is a mismatch in line numbers on my side, may I ask
> you where you got your sources from? downloaded a package? git? in the
> later case, do you know which branch?
>
> As you may I have, I have proposed a patch that should at least prevent
> the crash, but if you happend to have time to do the git bissect that would
> be helpful too!
>
> Best regards,
> Christophe.
>
>
> >
> > On Sat, Jun 15, 2013 at 7:11 AM, Christophe <christophe.cu...@free.fr
> >wrote:
> >
> > >
> > > ----- Juan Giordana <juangiord...@gmail.com> a écrit :
> > > > Hello,
> > > >
> > > > I followed the instructions on the README on how to make a backtrace
> > > (make
> > > > CFLAGS=-g), but couldn't find the output file on my home directory,
> tmp,
> > > or
> > > > GNUstep directory.
> > >
> > > Hello,
> > > Maybe the procedure for backtrace generation from the doc is not up to
> > > date, could I propose this instead:
> > >  - go into compilation directory
> > >  - create file 'commands' with these 3 lines:
> > > run --for-real
> > > bt
> > > quit
> > >
> > >  - execute this:
> > > script -c "gdb src/.libs/wmaker" debug.log < commands
> > >
> > > This will run wmaker inside GDB, providing the expectable commands to
> gdb
> > > and saving the output to file 'debug.log'. All you have to do is
> reproduce
> > > the problem; when wmaker will crash gdb will generate the backtrace and
> > > will quit afterwards.
> > >
> > > All you'll have to do then is share the "debug.log" if the procedure
> have
> > > worked.
> > >
> > >
> > > > Maybe this is related?
> > > >
> > > > wmaker(MonitorLoop(monitor.c:135)): warning: Window Maker exited due
> to a
> > > > crash (signal 11) and will be restarted.
> > > > wmaker(setSwPOptions(defaults.c:3018)): warning: Could not load image
> > > > "/usr/local/share/WindowMaker/Pixmaps/swback.png" for option
> > > > "SwitchPanelImages"
> > > > wmaker(setSwPOptions(defaults.c:3090)): warning: Could not load image
> > > > "/usr/local/share/WindowMaker/Pixmaps/swtile.png" for option
> > > > "SwitchPanelImages"
> > > >
> > > > I'll try 'git bisect' later.
> > > >
> > > >
> > > > On Wed, Jun 12, 2013 at 4:20 AM, Christophe <
> christophe.cu...@free.fr
> > > >wrote:
> > > >
> > > > >
> > > > > ----- Rodolfo García Peñas (kix) <k...@kix.es> a écrit :
> > > > > >
> > > > > > Juan Giordana <juangiord...@gmail.com> escribió:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I'm using Linux mint and just built the latest Windowmaker from
> > > the git
> > > > > > > repo and it crashed when I tried to switch windows with
> alt+tab.
> > > > > > >
> > > > > > > - I've created 5 workspaces and added some keyboard shortcuts
> to my
> > > > > config
> > > > > > > and selected the optoin to raise the windows while switching
> them
> > > with
> > > > > > > alt+tab
> > > > > > > - Went to the workspace 'www' opened chromium, opera, firefox
> and
> > > an
> > > > > xterm
> > > > > > > - Quickly pressing Alt+tab crashed WindowMaker
> > > > > > > - Not so quickly behaves poorly.
> > > > > > >
> > > > > > > Regards
> > > > > >
> > > > > > Hi Juan,
> > > > > >
> > > > > > could you help us with "git bisect" to find the wrong git commit?
> > > > > >
> > > > > > Thanks,
> > > > > > kix
> > > > > > Rodolfo García Peñas (kix)
> > > > > > http://www.kix.es/
> > > > >
> > > > > Hi Juan,
> > > > >
> > > > > May I suggest including a backtrace too? This often provides
> helpful
> > > > > information.
> > > > >
> > > > > Regards,
> > > > > Christophe.
> > > > >
> > > > >
> > >
> > >
>
>
> --
> To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
>

Attachment: wmaker-bad-commit.log
Description: Binary data

Reply via email to