DragonFly bugs List (threaded) for 2008-01
DragonFly BSD
DragonFly bugs List (threaded) for 2008-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [issue920] Incomplete backtrace in gdb


From: "Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>
Date: Thu, 17 Jan 2008 00:05:50 +0100

Matthew Dillon wrote:
    Also note that GCC-4 by default rolls up functions it thinks it
    can inline on a file-by-file basis.  So if function A calls function B
    and GCC thinks it can inline function B in function A, whether or
    not you've told it to, it will.  You'll then get an error for function
    B but the gdb backtrace will list the problem as being in function A.

yes, this is in so far annoying, because you can't properly "escape" from the inlined part. also, debugging symbols sometimes don't seem to work correctly.


    I've noticed this when trying to debug kernels.  I personally think
    its a mistake, along with the idiotic default numeric optimizations
    that break bounds checks.

i don't think that it yields a big benefit, but makes debugging harder. so i would rather not have it. maybe we should research on how to switch this auto-inlining off.


cheers
  simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \




[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]