GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  BUGLE-UNWINDSTACK (7)

NAME

bugle-unwindstack - recover a stack trace after a segmentation fault

CONTENTS

SYNOPSIS

filterset unwindstack

DESCRIPTION

Some OpenGL drivers (particularly proprietry drivers) are compiled without frame pointer information. The result is that if you pass a bad pointer to the driver, causing it to segfault, gdb(1) is unable to produce a stack trace showing that location of the fault. This filter-set uses some ugly hacks to try to correct this.

When using this filter-set and debugging your application in gdb(1), the segmentation fault will still leave you without a stack trace. However, if you continue running, you will get a second segmentation fault, at which point a stack trace is available.

Note that the call that causes the segmentation fault may not be the direct cause; for example, a bad pointer passed to glVertexPointer might only cause a segmentation fault in glDrawArrays. See also the bugle-checks(7) filter-set, which does some aggressive error-checking and can detect some of these conditions.

BUGS

The method used to recover the stack trace violates POSIX rules (and common sense) about the use of setjmp. It works for me under Linux with NVIDIA drivers, but your mileage might vary.

AUTHOR

bugle is written and maintained by Bruce Merry.

SEE ALSO

o

o bugle(3)

o

o bugle-checks(7)

o

o

setjmp(3)

Search for    or go to Top of page |  Section 7 |  Main Index


BUGLE 0.0.20091026 BUGLE-UNWINDSTACK (7) October 2007

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.