Part of Slepp's Projects — Pastebin — TURL — Imagebin — Filebin
Feedback -- English French German Japanese
Create Upload Newest Tools Donate

Paste Actions

Download Raw
Embed
Post to Twitter
Remove Paste

Paste Details

Raw format, 10 years 7 months old.

Advertising

Something
Tuesday, June 5th, 2007 at 12:40:55pm UTC 

  1. 10:13 < stuarta> where is the thread ID of the crashing thread in the Ubuntu backtraces?
  2. 10:14 < stuarta> dammit, they've cut off the most important 3 lines in the gdb backtrace...
  3. 10:15 < gardengnome> stuarta: have you read yesterday's discussion?
  4. 10:15 < stuarta> yeah, i saw much of it while lurking
  5. 10:15 < gardengnome> it seems the backtraces are useless anyways. :(
  6. 10:16 < stuarta> i'm currently digging around the aport stuff on the website.
  7. 10:16 < gardengnome> we'll be working on creating usable backtraces.
  8. 10:17 < stuarta> do you know the bit i mean in the gdb backtrace?
  9. 10:18 < gardengnome> no, i actually didn't look at the backtraces themselves
  10. 10:18 < gardengnome> to me, it's just gibberish. :)
  11. 10:19 < stuarta> http://pastebin.ca/539602
  12. 10:19 < stuarta> that's the 3 missing lines off the top of the backtrace.
  13. 10:19 < gardengnome> stuarta: which ticket number is that?
  14. 10:20 < stuarta> tells me 1. why it died 2. where it died (threadid & file, linenum)
  15. 10:20 < stuarta> gardengnome: that's just a random ffmpeg backtrace i had lying around
  16. 10:20 < gardengnome> ah
  17. 10:20 < stuarta> but it illustrates the stuff i'd like in backtraces (as well as useful line
  18.                  numbers from the dbg build)
  19. 10:20 < gardengnome> stuarta: i suppose we don't get those because we --enable-proc-opt. :)
  20. 10:20 < gardengnome> sure.
  21. 10:21 < stuarta> not true. i enable proc opt and still get them
  22. 10:21 < gardengnome> interesting.
  23. 10:21 < stuarta> i do however always build the debug release
  24. 10:21 < gardengnome> is apport broken then?
  25. 10:21 < gardengnome> stuarta: we're also doing --compile-type=debug
  26. 10:23 < stuarta> imagine for a moment you had a multithreaded program with several threads doing
  27.                  similar things
  28. 10:23  * gardengnome does so
  29. 10:23 < stuarta> you'd have trouble working out which thread was at fault if they are all working
  30.                  in the same area of code
  31. 10:24 < stuarta> mythbackend often does this, if say you are recording 2 different things at once
  32. 10:24 < gardengnome> true
  33. 10:25 < Anduin> we should add 'info program' to the debug howto
  34. 10:27 < gardengnome> stuarta: that's an interesting finding. i'll forward it to someone more
  35.                      knowledgeable.
  36. 10:28 < stuarta> thanks
  37. 10:33 < gbee> the extra debugging symbols would enable use to find the exact line at which the
  38.               crashing occurs e.g. #3536 just says that it occured in GuideGrid::fillProgramRowInfos
  39. 10:34 < gbee> that function is nearly 240 lines long - so figuring out precisely where or why it
  40.               crashes is that much harder
  41. 10:35 < gardengnome> like the proverbial needle in a haystack :(
  42. 10:35 < stuarta> i've a good mind to close 3565 as fixed in head
  43. 10:36 < gbee> gardengnome: it's doable, but it's nowhere near as quick and easy as it would be if
  44.               we knew the precise line
  45. 10:36 < gbee> I actually really like the idea of automated backtraces and reporting tools, if you
  46.               can get apport providing the right information then it would be very valuable
  47. 10:37 < gbee> I can't think how many people claim that mythfrontend/mythbackend has segfaulted on
  48.               them at some time, but most of those people cannot produce a backtrace or can't even
  49.               reproduce the crash
  50. 10:38 < gardengnome> i bet that "most people" are too lazy. that's why i like the idea of having
  51.                      apport generate backtraces automatically
  52. 10:39 < stuarta> i'll agree, it's a lot better than some of the other automated backtrace
  53.                  generators.
  54. 10:39 < gbee> It could improve the stability of myth for most people a lot if these edge and corner
  55.               case segfaults were addressed
  56. 10:40 < gardengnome> we just need to get good backtraces :)
  57. 10:42 < gardengnome> launchpad makes me want to bang my head against a wall, though
  58. 10:44 < gardengnome> i created a "blueprint" last night:
  59.                      https://blueprints.launchpad.net/mythtv/+spec/mythtv-sane-dbg-symbols
  60. 10:44 < gardengnome> i'll update it with today's results. thanks for the input :)
  61. 10:44 < gardengnome> i created a "blueprint" last night:
  62.                      https://blueprints.launchpad.net/mythtv/+spec/mythtv-sane-dbg-symbols
  63. 10:44 < gardengnome> i'll update it with today's results. thanks for the input :)

advertising

Update the Post

Either update this post and resubmit it with changes, or make a new post.

You may also comment on this post.

update paste below
details of the post (optional)

Note: Only the paste content is required, though the following information can be useful to others.

Save name / title?

(space separated, optional)



Please note that information posted here will not expire by default. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.

comments powered by Disqus
worth-right
worth-right
worth-right