From: Daniel Jacobowitz <drow@false.org>
To: Hamish Rodda <rodda@kde.org>
Cc: gdb@sources.redhat.com
Subject: Re: Unwinding stack past main() when it has another name
Date: Wed, 15 Jun 2005 16:37:00 -0000 [thread overview]
Message-ID: <20050615163658.GA18795@nevyn.them.org> (raw)
In-Reply-To: <200506160112.58152.rodda@kde.org>
On Thu, Jun 16, 2005 at 01:12:54AM +1000, Hamish Rodda wrote:
> Yep... here's a snippet:
>
> #21 0x00002aaaacab22fa in QApplication::exec () at
> kernel/qapplication.cpp:2522
> #22 0x00002aaaaabd0a84 in kdemain (argc=<value optimized out>,
> argv=0x7fffffbd8ce8) at /opt/kde4/src/kdebase/kate/app/kwritemain.cpp:696
> #23 0x00002aaaaf227d95 in __libc_start_main () from /lib/libc.so.6
> #24 0x00000000004007ea in _start () at ../sysdeps/x86_64/elf/start.S:113
>
> In gdb 6.3 on amd64, this trace would be follwed by approx 800 - 1000 useless
> "frames".
>
> I don't exactly know why or how the kdemain() function works, but I know it
> has something to do with kdeinit... there's some comments in the source in
> the kde svn repository, under kdelibs/kinit/*
Presumably main() tail called to kdemain. Does the backtrace stop OK
at _start? If so, is there really a problem?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-15 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 12:46 Hamish Rodda
2005-06-15 14:16 ` Daniel Jacobowitz
2005-06-15 15:14 ` Hamish Rodda
2005-06-15 16:37 ` Daniel Jacobowitz [this message]
2005-06-16 7:42 ` Hamish Rodda
2005-06-16 13:23 ` Daniel Jacobowitz
2005-06-16 21:22 ` Steven Johnson
2005-06-16 22:05 ` Daniel Jacobowitz
2005-06-16 22:46 ` Steven Johnson
2005-06-17 11:21 ` Richard Earnshaw
2005-06-18 13:13 ` Eli Zaretskii
2005-06-16 23:36 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050615163658.GA18795@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=rodda@kde.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox