gdb --batch --quiet -ex "thread apply all bt full" -ex "quit" ${exe} ${corefile}

Print stack trace of a core file without needing to enter gdb interactively

This does almost the same thing as the original, but it runs the full backtrace for _all_ the threads, which is pretty important when reporting a crash for a multithreaded software, since more often than not, the signal handler is executed in a different thread than the crash happened.

5
By: Flameeyes
2010-07-06 14:49:03

2 Alternatives + Submit Alt

What Others Think

Hello, I want store the 2 macros output into a string file. how to do that ? coregdb --batch --quit -ex "bt" -ex "quit" "/x/eng/cs-cores1/bug/xx/xx/xxxx/xxxx/xxx.92242.536944628.2018-02-01.21_09_04.ucore.bz2" I want to store the output of panicString and backtrace(bt) in a string using perl script how to do that ??
srinivasng · 11 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: