Re: gdb debug core file?

[stanton arch]

Hmmm, I tried that but I can't see the backtrace for some reason
inside of emacs, but in a normal shell is fine.

If I do from shell:
> gdb myprog myprog.core
[snipped...]
Type "apropos word" to search for commands related to "word"...
Reading symbols from myprog...done.

[New process 1]
Core was generated by `myprog'.
Program terminated with signal SIGABRT, Aborted.
#0  0xbb1bfed7 in _lwp_kill () from /usr/lib/libc.so.12
(gdb) bt
#0  0xbb1bfed7 in _lwp_kill () from /usr/lib/libc.so.12
#1  0xbb1bfe78 in raise () from /usr/lib/libc.so.12
#2  0xbb1bfa92 in abort () from /usr/lib/libc.so.12
...

but inside of emacs I get:
 gdb -i=mi --core=./myprog.core ./myprog
[snipped...]
Reading symbols from myprog...done.

[New process 1]
Core was generated by `myprog'.
Program terminated with signal SIGABRT, Aborted.
(gdb) bt
Invalid selected thread.
(gdb)

It is only this particular program I seem to have issues, a simple
hello_world.c works fine in emacs and shell.

Is there some gdb command I need to run inside of emacs first to view
backtrace, or any other ideas?

Thanks