Re: bug

[Michael Snyder]

Markus Plannerer wrote:
> 
> Hello,
> 
> gdb doesn't work with my application when it comes into the
> function "popen()". After geting information about the
> thread with "info thread" the message "Speicherschutzverletzung"
> comes up and that is the end of gdb. "Speicherschutzverletzung"
> means "segmentation vault". The environment is C++, SuSE Linux 8.0,
> gcc 2.95.3 (SuSE), gdb 5.1.1, and the application is a CAD-System
> with Qt, SoQt, SGI Inventor, so it is not possible to make a
> small sample.
> 
> Thank's
> Markus

Was there a coredump?  Try this:

        % gdb gdb core
        (gdb) backtrace

Send us what you get.

> 
> Here ist the log:
> 
> erl/boxd> gdb boxsqt
> GNU gdb 5.1.1
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-suse-linux"...
> (gdb) run -r
> Starting program: /usr/people/erl/boxd/boxsqt -r
> [New Thread 1024 (LWP 15599)]
> Qt: gdb: -nograb added to command-line options.
>           Use the -dograb option to enforce grabbing.
> [New Cannot find thread 2049: invalid thread handle
> (gdb) info thread
> * 1 Thread 1024 (LWP 15607)  [No stack.]
> Speicherschutzverletzung
> 
> _______________________________________________
> Bug-gdb mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-gdb