Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug navigating through menus
05-31-2011, 05:47 PM
Post: #1
Bug navigating through menus
Code:
gdb  --args vdrift -multithreaded
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "i686-linux-gnu".
Para las instrucciones de informe de errores, vea:
<http://www.gnu.org/software/gdb/bugs/>...
Leyendo símbolos desde /usr/local/bin/vdrift...hecho.
(gdb) run
Starting program: /usr/local/bin/vdrift -multithreaded
[Depuración de hilo usando libthread_db enabled]
INFO: Multithreading enabled: 2 processors
INFO: Starting VDrift: development-full, Version: 3131, O/S: Unix-like
INFO: Home directory: /home/antonio
INFO: Settings file: /home/antonio/.vdrift/VDrift.config
INFO: Data directory: /usr/local/share/games/vdrift/data
      DATA_DIR: /usr/local/share/games/vdrift/data
INFO: Temporary directory: /home/antonio/.vdrift/tmp
INFO: Log file: /home/antonio/.vdrift/log.txt
[Nuevo Thread 0x2e75b70 (LWP 4723)]
[Thread 0x2e75b70 (LWP 4723) terminado]
INFO: SDL initialization successful
INFO: SDL video query was successful
INFO: Enabling antialiasing: 4X
INFO: Display change was successful: 1152x720x32 24z fullscreen=0
INFO: GL Renderer: GeForce 9600 GT/PCI/SSE2/3DNOW!
INFO: GL Vendor: NVIDIA Corporation
INFO: GL Version: 3.3.0 NVIDIA 270.41.06
INFO: Initialized GLEW 1.6.0
INFO: Loading /usr/local/share/games/vdrift/data/shaders/gl3/vdrift1.rhr...
INFO: Loaded /usr/local/share/games/vdrift/data/shaders/gl3/vdrift1.rhr
INFO: GL3 initialization successful
INFO: 0 joysticks found.
INFO: Loading car controls from: /home/antonio/.vdrift/controls.config
[Nuevo Thread 0x2e75b70 (LWP 4724)]
INFO: Sound initialization information:
INFO: Obtained audio device:
      Frequency: 44100
      Format: 32784
      Bits per sample: 16
      Channels: 2
      Silence: 0
      Samples: 1024
      Size: 4096
      Sound initialization successful
INFO: Loaded fonts successfully
INFO: Loaded GUI successfully

Program received signal SIGSEGV, Segmentation fault.
0x01778140 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06
(gdb) c
Continuando.
[Thread 0x2e75b70 (LWP 4724) terminado]

Program received signal SIGSEGV, Segmentation fault.
0x01778140 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06

Open vdrift -> Single Race -> back -> Single race => CRASH!
Find all posts by this user
Quote this message in a reply
06-01-2011, 10:32 AM
Post: #2
 
I was unable to reproduce this crash. Can you run it again in gdb, this time without the -multithreaded option and when the crash happens do "bt" to get a backtrace?
Find all posts by this user
Quote this message in a reply
06-01-2011, 10:46 AM
Post: #3
 
Code:
gdb vdrift
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "i686-linux-gnu".
Para las instrucciones de informe de errores, vea:
<http://www.gnu.org/software/gdb/bugs/>...
Leyendo símbolos desde /usr/local/bin/vdrift...hecho.
(gdb) r
Starting program: /usr/local/bin/vdrift
[Depuración de hilo usando libthread_db enabled]
INFO: Multi-processor system detected.  Run with -multithreaded argument to enable multithreading (EXPERIMENTAL).
INFO: Starting VDrift: development-full, Version: 3131, O/S: Unix-like
INFO: Home directory: /home/antonio
INFO: Settings file: /home/antonio/.vdrift/VDrift.config
INFO: Data directory: data
      DATA_DIR: /usr/local/share/games/vdrift/data
INFO: Temporary directory: /home/antonio/.vdrift/tmp
INFO: Log file: /home/antonio/.vdrift/log.txt
[Nuevo Thread 0x2e75b70 (LWP 1881)]
INFO: SDL initialization successful
INFO: SDL video query was successful
INFO: Enabling antialiasing: 4X
[Thread 0x2e75b70 (LWP 1881) terminado]
INFO: Display change was successful: 1152x720x32 24z fullscreen=0
INFO: GL Renderer: GeForce 9600 GT/PCI/SSE2/3DNOW!
INFO: GL Vendor: NVIDIA Corporation
INFO: GL Version: 3.3.0 NVIDIA 270.41.06
INFO: Initialized GLEW 1.6.0
INFO: Loading data/shaders/gl3/vdrift1.rhr...
INFO: Loaded data/shaders/gl3/vdrift1.rhr
INFO: GL3 initialization successful
INFO: 0 joysticks found.
INFO: Loading car controls from: /home/antonio/.vdrift/controls.config
[Nuevo Thread 0x2e75b70 (LWP 1882)]
INFO: Sound initialization information:
INFO: Obtained audio device:
      Frequency: 44100
      Format: 32784
      Bits per sample: 16
      Channels: 2
      Silence: 0
      Samples: 1024
      Size: 4096
      Sound initialization successful
INFO: Loaded fonts successfully
INFO: Loaded GUI successfully

Program received signal SIGSEGV, Segmentation fault.
0x01778140 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06
(gdb) bt
#0  0x01778140 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06
(gdb)

Sorry but that is only what bt returns. I don't know how to compile vdrift with debug simbols with scons. If you tell me how I'll do it in ten minutes. Thanks.
Find all posts by this user
Quote this message in a reply
06-01-2011, 05:01 PM
Post: #4
 
Try:
Code:
scons -h
. Afaik the default build is release=0, means debug mode -g3.

Are you still experiencing this issues with the latest revision? I've had introduced a number of bugs with r3119.

Edit: scons help parameter
Find all posts by this user
Quote this message in a reply
06-01-2011, 06:25 PM
Post: #5
 
NaN Wrote:Try:
Code:
scons -h
. Afaik the default build is release=0, means debug mode -g3.

Are you still experiencing this issues with the latest revision? I've had introduced a number of bugs with r3119.

Edit: scons help parameter

release=0 compiled now from 3132 and stills happening.
Find all posts by this user
Quote this message in a reply
06-01-2011, 10:35 PM
Post: #6
 
Without more information, all I can say is that the crash is happening in the NVIDIA driver. I can't say what VDrift is doing that causes the crash. It works fine on my machine without crashing. You could try a different nvidia driver version.
Find all posts by this user
Quote this message in a reply
06-02-2011, 03:31 AM
Post: #7
 
@antoniovazquez: Can you upload your VDrift.config?
Find all posts by this user
Quote this message in a reply
06-02-2011, 08:46 AM
Post: #8
 
NaN Wrote:@antoniovazquez: Can you upload your VDrift.config?

There was a release = True there. Disabing it and testing. Thanks.
Find all posts by this user
Quote this message in a reply
06-02-2011, 09:55 AM
Post: #9
 
Same problem, no debug simbols appart from what I've given before.... humm.
Find all posts by this user
Quote this message in a reply
06-02-2011, 10:55 AM
Post: #10
 
@antoniovazquez
I'd like to test with your .vdrift/VDrift.config file. I don't think it is going to trigger the bug I guess it is a driver issue, but who knows?
Code:
[control]
autoclutch = true
autotrans = true
button_ramp = 5
mousegrab = false
speed_sens_steering = 1

[display]
FOV = 45
anisotropic = 0
antialiasing = 0
bloom = false
camerabounce = 1
contrast = 1
depth = 16
fullscreen = false
height = 600
....
Find all posts by this user
Quote this message in a reply
06-02-2011, 11:42 AM
Post: #11
 
Code:
[control]
autoclutch = true
autotrans = true
button_ramp = 5
mousegrab = true
speed_sens_steering = 1

[display]
FOV = 67.5
anisotropic = 16
antialiasing = 4
bloom = true
camerabounce = 1
contrast = 1
depth = 32
fullscreen = false
height = 720
input_graph = false
language = English
lighting = 2
mph = false
normalmaps = true
racingline = false
reflections = 2
shaders = true
shadow_distance = 1
shadow_quality = 2
shadows = true
show_fps = false
show_hud = true
skin = simple
texture_size = large
trackmap = true
view_distance = 1000
width = 1152
zdepth = 24

[game]
ai_difficulty = 1
antilock = true
camera_mode = incar
number_of_laps = 1
opponent = XS/XS.car
opponent_color = 1,1,1
opponent_paint = default
player = CO/CO.car
player_color = 0.0555556,0.0555556,0.0555556
player_paint = default
record = false
reverse = false
selected_replay = 1
track = nuerburgring_nordschleife
track_dynamic = true
traction_control = true
vehicle_damage = false

[joystick]
calibrated = false
ff_device = /dev/input/event0
ff_gain = 2
ff_invert = false
hgateshifter = false
two_hundred = false
type = joystick

[sound]
volume = 1

Sorry for my mistake. I don't think configuration is triggering the bug as it happens in various resolutions... Thanks
Find all posts by this user
Quote this message in a reply
06-03-2011, 04:11 PM
Post: #12
 
It also happens when I try to switch any car in single race....
Code:
gdb vdrift
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "i686-linux-gnu".
Para las instrucciones de informe de errores, vea:
<http://www.gnu.org/software/gdb/bugs/>...
Leyendo símbolos desde /usr/local/bin/vdrift...hecho.
(gdb) run
Starting program: /usr/local/bin/vdrift
[Depuración de hilo usando libthread_db enabled]
INFO: Multi-processor system detected.  Run with -multithreaded argument to enable multithreading (EXPERIMENTAL).
INFO: Starting VDrift: development-full, Version: 3135, O/S: Unix-like
INFO: Home directory: /home/antonio
INFO: Settings file: /home/antonio/.vdrift/VDrift.config
INFO: Data directory: /usr/local/share/games/vdrift/data
      DATA_DIR: /usr/local/share/games/vdrift/data
INFO: Temporary directory: /home/antonio/.vdrift/tmp
INFO: Log file: /home/antonio/.vdrift/log.txt
[Nuevo Thread 0x2e75b70 (LWP 2020)]
INFO: SDL initialization successful
INFO: SDL video query was successful
INFO: Enabling antialiasing: 4X
[Thread 0x2e75b70 (LWP 2020) terminado]
INFO: Display change was successful: 1152x720x32 24z fullscreen=0
INFO: GL Renderer: GeForce 9600 GT/PCI/SSE2/3DNOW!
INFO: GL Vendor: NVIDIA Corporation
INFO: GL Version: 3.3.0 NVIDIA 270.41.06
INFO: Initialized GLEW 1.6.0
INFO: Loading /usr/local/share/games/vdrift/data/shaders/gl3/vdrift1.rhr...
INFO: Loaded /usr/local/share/games/vdrift/data/shaders/gl3/vdrift1.rhr
INFO: GL3 initialization successful
INFO: 0 joysticks found.
INFO: Loading car controls from: /home/antonio/.vdrift/controls.config
[Nuevo Thread 0x2e75b70 (LWP 2021)]
INFO: Sound initialization information:
INFO: Obtained audio device:
      Frequency: 44100
      Format: 32784
      Bits per sample: 16
      Channels: 2
      Silence: 0
      Samples: 1024
      Size: 4096
      Sound initialization successful
INFO: Loaded fonts successfully
INFO: Loaded GUI successfully

Program received signal SIGSEGV, Segmentation fault.
0x01778140 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06
(gdb) bt
#0  0x01778140 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.270.41.06
(gdb)
Find all posts by this user
Quote this message in a reply
06-03-2011, 05:07 PM
Post: #13
 
Looks like a driver bug.

Maybe there is a way to identify the call causing the segfault. Would be interesting to see the opengl trace. I am using gpuperfstudio under win32. I think there is a tool available for linux, haven't tested it by myself yet: In order to view links, you must have to reply to this thread.
Find all posts by this user
Quote this message in a reply
06-05-2011, 06:54 AM
Post: #14
 
NaN Wrote:Looks like a driver bug.

Maybe there is a way to identify the call causing the segfault. Would be interesting to see the opengl trace. I am using gpuperfstudio under win32. I think there is a tool available for linux, haven't tested it by myself yet: In order to view links, you must have to reply to this thread.

I've done a tracing by reading the instructions in README. I don't know how to continue debugging this. Should I report this bug elsewhere? Thanks!

My trace: In order to view links, you must have to reply to this thread.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)