Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - General
User Name
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.


  Search this Thread
Old 07-19-2005, 11:40 PM   #1
Registered: Nov 2004
Location: Near Lansing, MI , USA
Distribution: Mainly just Mandriva these days.
Posts: 315

Rep: Reputation: 30
Help With Doing a Back Trace Please

I'm having a problem with certain programs crashing and in order to get help from the authors (the crashes are caused by dri when I run OpenGL programs) I'd like to reproduce the crash, then do a back trace to give them information about it. I'm having issues, and I'm hoping someone knows how to help me with them. The directions they give to do the back trace are to run the following commands:

ulimit -c unlimited
glxgears (this runs a 3D program to reproduce the crash)
gdb -c core 'which glxgears'

Following the third command I get an error:

This GDB was configured as "i586-mandrake-linux-gnu"...which glxgears: No such file or directory.

/home/springshades/core: No such file or directory.

However, the program continues to run. Now, after the fourth command I get:

No stack.

Anyone know what this problem could be? I have NO experience with back traces, so I don't even know what to google for. I've tried googling back trace, but it seems like this or similar sets of commands work for just about everyone else. Could this be a Mandriva LE 2005 bug? Specific to my distro or something? I'm using the kernel that comes with the distro, haven't recompiled it.
Old 07-20-2005, 06:51 AM   #2
Registered: Apr 2005
Location: England
Distribution: Gentoo
Posts: 142

Rep: Reputation: 16
Try running just:
gdb glxgears
You should then get a gdb prompt, just type run
(gdb) run
GDB will spit out lots of info, copy and paste this into a text file.

Hope that helps
Old 07-20-2005, 08:11 PM   #3
Registered: Nov 2004
Location: Near Lansing, MI , USA
Distribution: Mainly just Mandriva these days.
Posts: 315

Original Poster
Rep: Reputation: 30
Thanks, this probably should have helped, but still issues. I'm wondering if maybe the program is seg faulting before the debugger can even get any information. I'm not sure. I'm going to give up on this approach for now, thanks for your help.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
c coding trace bruse Linux - Newbie 2 07-13-2005 04:25 PM
Stack trace ust Linux - General 0 02-27-2004 02:30 AM
loging trace consty Linux - Security 1 02-22-2004 02:49 PM
way to trace IP's back to the source scottpioso Linux - Software 22 12-29-2003 10:52 AM
Trace hacker? mikeshn Linux - Security 8 04-17-2003 01:30 PM > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 08:26 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration