Threaded Mode | Linear Mode

**gregory** · 04-06-2011 08:01 PM

Actually you could stop to point 4, which is the bad segmentation fault. It seem you never reach SDL_VideoInit which must be called before your segmentation fault !!!
3a/ break SDL_video.c:1112
3b/ break SDL_VideoInit
4/ print _this <= must be 0. The program must stop in the breakpoint 3a.
5/ step twice. Normally you must enter SDL_VideoInit. Either you do not enter the if code or the function call go in an unkwnon place ! Check where you are (bt, list ).

For onepad, ask mandriva to get the patch in their rpm. Very good for others. Temporary workaround of the missing scrolling there is a combination to move easily windows (try alt-left click / or middle or left depend of the desktop enviroment Wink

)

dubigrasu · 04-07-2011 08:06 AM

@tuxgamer

Quote:btw, can you test xbox360 with Zeropad plugin, in there have Forcefeedback option.

At this moment I don't have any traces of PCSX2 left in my system, I'm waiting for the new release and start again fresh Smile

As for notifying Mandriva devs about the SDL issue, there is no need.
There is already a bug report about it, but very few hands at work, all busy with the new release.
Mandriva is in pretty bad shape now. Sad

**gregory** · 04-07-2011 10:58 AM

Did they have the patch attached in the bug report, just include a patch is normally not too much work.

tuxgamer · 04-07-2011 11:25 AM

(04-06-2011 08:01 PM)gregory Wrote: Actually you could stop to point 4, which is the bad segmentation fault. It seem you never reach SDL_VideoInit which must be called before your segmentation fault !!!
3a/ break SDL_video.c:1112
3b/ break SDL_VideoInit
4/ print _this <= must be 0. The program must stop in the breakpoint 3a.
5/ step twice. Normally you must enter SDL_VideoInit. Either you do not enter the if code or the function call go in an unkwnon place ! Check where you are (bt, list ).

Thanks for the reply,

here the result:

Code:

[ai@Mandriva_2010_Spring bin]$ gdb pcsx2-dbg 

GNU gdb (GDB) 7.1-1mdv2010.1 (Mandriva Linux release 2010.1)

Copyright (C) 2010 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later &lt;http://gnu.org/licenses/gpl.html&gt;

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "i586-mandriva-linux-gnu".

For bug reporting instructions, please see:

&lt;http://www.gnu.org/software/gdb/bugs/&gt;...

Reading symbols from /home/ai/Game/pcsx2-svn/bin/pcsx2-dbg...done.

(gdb) run

Starting program: /home/ai/Game/pcsx2-svn/bin/pcsx2-dbg 

[Thread debugging using libthread_db enabled]

Interface is initializing.  Entering Pcsx2App::OnInit!

Applying operating system default language...

Detaching after fork from child process 2636.

Detaching after fork from child process 2637.

Detaching after fork from child process 2638.

Command line parsing...

Command line parsed!

[New Thread 0xb6077b70 (LWP 2639)]

Detaching after fork from child process 2640.

[New Thread 0xb5622b70 (LWP 2643)]

[Thread 0xb5622b70 (LWP 2643) exited]

^C

Program received signal SIGINT, Interrupt.

0xffffe424 in __kernel_vsyscall ()

Missing debug package(s), you should install: SDL12-debug-1.2.14-3mdv2010.2.i586 aalib-debug-1.4.0-0.rc5.19mdv2010.1.i586 atk1.0-debug-1.30.0-1mdv2010.1.i586 cairo-debug-1.9.14-0.2mdv2010.1.i586 directfb-debug-1.4.3-2mdv2010.1.i586 fontconfig-debug-2.8.0-2mdv2010.1.i586 freetype2-debug-2.3.12-1.5mdv2010.1.i586 gcc-debug-4.4.3-2mnb2.i586 glib2.0-debug-2.24.1-1mdv2010.1.i586 glibc-debug-2.11.1-8.2mnb2.i586 gtk+2.0-debug-2.20.1-1mdv2010.1.i586 ia_ora-gnome-debug-1.0.24-1mdv2010.1.i586 jbigkit-debug-2.0-4mdv2010.1.i586 libart_lgpl-debug-2.3.21-1mdv2010.1.i586 libcanberra-debug-0.24-2mdv2010.1.i586 libggi-debug-2.2.2-14mdv2010.1.i586 libgii-debug-1.0.2-13mdv2010.1.i586 libgnomecanvas-debug-2.30.1-1mdv2010.1.i586 libgnomeprint-debug-2.18.7-1mdv2010.1.i586 libgnomeprintui-debug-2.18.5-1mdv2010.1.i586 libice-debug-1.0.6-2mdv2010.1.i586 libjpeg-debug-8a-1mdv2010.1.i586 libogg-debug-1.2.0-1mdv2010.1.i586 libpng-debug-1.2.43-1.1mdv2010.1.i586 libsm-debug-1.1.1-2mdv2010.1.i586 libtiff-debug-3.9.2-2.2mdv2010.1.i586 libtool-debug-2.2.6b-2mdv2010.1.i586 libvorbis-debug-1.3.1-1mdv2010.1.i586 libx11-debug-1.3.3-1mdv2010.1.i586 libxau-debug-1.0.5-2mdv2010.1.i586 libxcb-debug-1.6-1mdv2010.1.i586 libxcomposite-debug-0.4.1-1mdv2010.1.i586 libxcursor-debug-1.1.10-2mdv2010.1.i586 libxdamage-debug-1.1.2-1mdv2010.1.i586 libxdmcp-debug-1.0.3-2mdv2010.1.i586 libxext-debug-1.1.1-2mdv2010.1.i586 libxfixes-debug-4.0.4-1mdv2010.1.i586 libxi-debug-1.3-1mdv2010.1.i586 libxinerama-debug-1.1-1mdv2010.1.i586 libxml2-debug-2.7.7-1.1mdv2010.1.i586 libxrandr-debug-1.3.0-3mdv2010.1.i586 libxrender-debug-0.9.5-2mdv2010.1.i586 libxxf86dga-debug-1.1.1-1mdv2010.1.i586 libxxf86vm-debug-1.1.0-1mdv2010.1.i586 ncurses-debug-5.7-4.20091227.1mdv2010.1.i586 pango-debug-1.28.0-1mdv2010.1.i586 pcre-debug-8.02-1mdv2010.1.i586 pixman-debug-0.18.2-1mdv2010.1.i586 slang-debug-2.2.2-1mdv2010.1.i586 tdb-debug-1.2.1-1mdv2010.1.i586 zlib-debug-1.2.3-15mdv2010.1.i586

(gdb) break SDL_video.c:1112

Breakpoint 1 at 0xb4733e66: file /home/ai/Game/pcsx2-svn/3rdparty/SDL-1.3.0-5387/src/video/SDL_video.c, line 1112.

(gdb) break SDL_VideoInit

Breakpoint 2 at 0xb473280a: file /home/ai/Game/pcsx2-svn/3rdparty/SDL-1.3.0-5387/src/video/SDL_video.c, line 419.

(gdb) print _this

$1 = (SDL_VideoDevice *) 0x0

(gdb) bt

#0  0xffffe424 in __kernel_vsyscall ()

#1  0xb787cb16 in poll () from /lib/i686/libc.so.6

#2  0xb7192ceb in g_poll () from /usr/lib/libglib-2.0.so.0

#3  0xb7c2060a in wxapp_poll_func (ufds=0xa13cb30, nfds=2, timeout=-1) at src/gtk/app.cpp:266

#4  0xb7185805 in ?? () from /usr/lib/libglib-2.0.so.0

#5  0xb7185f07 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0

#6  0xb74a0a19 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0

#7  0xb7c3b5da in wxEventLoop::Run (this=0xa18f8c8) at src/gtk/evtloop.cpp:76

#8  0xb7cd615f in wxAppBase::MainLoop (this=0xa062540) at src/common/appcmn.cpp:312

#9  0xb7cd5cff in wxAppBase::OnRun (this=0xfffffdfc) at src/common/appcmn.cpp:367

#10 0xb7ef48f3 in wxEntry (argc=@0xb7fc182c, argv=0xa0515c0) at src/common/init.cpp:448

#11 0xb7ef4ad6 in wxEntry (argc=@0xbfffed90, argv=0xbfffee34) at src/common/init.cpp:460

#12 0x081a7cae in main (argc=1, argv=0xbfffee34) at /home/ai/Game/pcsx2-svn/pcsx2/gui/AppMain.cpp:39

(gdb) list

30

31      #include "Utilities/IniInterface.h"

32

33      #include &lt;wx/stdpaths.h&gt;

34

35      #ifdef __WXMSW__

36      #       include &lt;wx/msw/wrapwin.h&gt;              // needed to implement the app!

37      #endif

38

39      IMPLEMENT_APP(Pcsx2App)

(gdb)

I don't understand with the point in step 4, i must enter command "SDL_VideoInit" or go back to Step 2 or Just Stop ?

for Mandriva, i don't know hoe to contact Mandriva Dev team.

tuxgamer · 04-07-2011 11:30 AM

(04-07-2011 08:06 AM)dubigrasu Wrote: @tuxgamer
At this moment I don't have any traces of PCSX2 left in my system, I'm waiting for the new release and start again fresh

As for notifying Mandriva devs about the SDL issue, there is no need.
There is already a bug report about it, but very few hands at work, all busy with the new release.
Mandriva is in pretty bad shape now.

hmm, okay, i hpe you can test in next version, i saw in SVN Change, there is version 0.9.8 things, i hope the Dev Team gonna release v0.9.8 soon.

yeah, Mandriva in Bad Shape, but This the first distro i use ( accutually mandrake 8.0), so it's kinda first love to me.that's why no metter what, i still gonna use mandriva.

**gregory** · 04-07-2011 11:41 AM

Sorry, here some basic knowledge.
1/ a program is a (big) sequence of instruction. A function is a group of instruction to avoid to repeat them n time. you just call the function once.
2/ gdb allow to controle the execution flow. You can execute only 1 instruction or several. Breakpoint allow to stop the program when you encounter them nut you must run. When you have gdb control (console), the program is stopped and no instruction is executed.

So after the setup of the breakpoint you must type run to resume the execution flow of the program. When gdb encounter a breakpoint, it will tell you and give you back the control.

dubigrasu · 04-07-2011 12:08 PM

@ tux

Quote:for Mandriva, I don't know how to contact Mandriva Dev team.

OK, I'll do it.

**arcum42** · 04-07-2011 01:40 PM

(04-07-2011 11:30 AM)tuxgamer Wrote: hmm, okay, i hpe you can test in next version, i saw in SVN Change, there is version 0.9.8 things, i hope the Dev Team gonna release v0.9.8 soon.

yeah, Mandriva in Bad Shape, but This the first distro i use ( accutually mandrake 8.0), so it's kinda first love to me.that's why no metter what, i still gonna use mandriva.

Interesting. I'd figured most of the Mandriva people would be going to Mageia at this point, since Mandriva fired most of their developers, and a lot of them formed Mageia as a fork of Mandriva.

Looks like they even have a beta out, which is interesting, since they didn't have a release last time I'[d looked...

dubigrasu · 04-07-2011 04:13 PM

@arcum42

Quote:Interesting. I'd figured most of the Mandriva people would be going to Mageia at this point, since Mandriva fired most of their developers, and a lot of them formed Mageia as a fork of Mandriva.

Looks like they even have a beta out, which is interesting, since they didn't have a release last time I'[d looked...

We're still undecided Smile

Yes, while Mandriva still carries the name, very very few old devs are still there. There is almost no connection with the old Mandy other than the name.

Current Mandriva has (only) the name, while Mageia has the spirit. Though choice for old users like Tuxgamer and me.
They will both have the final release in June.

tuxgamer · 04-08-2011 04:30 AM

(04-07-2011 11:41 AM)gregory Wrote: Sorry, here some basic knowledge.
1/ a program is a (big) sequence of instruction. A function is a group of instruction to avoid to repeat them n time. you just call the function once.
2/ gdb allow to controle the execution flow. You can execute only 1 instruction or several. Breakpoint allow to stop the program when you encounter them nut you must run. When you have gdb control (console), the program is stopped and no instruction is executed.

So after the setup of the breakpoint you must type run to resume the execution flow of the program. When gdb encounter a breakpoint, it will tell you and give you back the control.

thanks for the reply.

hmmm, sory if i'am not smart enough Wacko

i will try it again tonight. Laugh

(i'am still at workplace right now)

Threaded Mode \| Linear Mode Linux - Compile Guide and Support
Author	Message