Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: gdb@sourceware.org
Subject: debugging uClinux application with GDB simulator
Date: Tue, 10 Oct 2017 09:12:00 -0000	[thread overview]
Message-ID: <20171010091214.GC7617@waldemar-brodkorb.de> (raw)

Hi GDB hackers,

I would like to debug an issue with vfork() function
from uClibc-ng for h8/300 architecture.

How it is supposed to work?

I can successfully load a Linux kernel with piggyback
initramfs and the sash shell in GDB simulator.
As soon as I try to exec another application it fails.
I think it might be a bug in vfork function.
As it is implemented in assembly I can not try to do
simple printf debugging.

The binary format used for this architecture is FLAT
and all C library functions are statically linked into
the sash binary.

As I start the GDB simulator with the kernel I can not
break into vfork() as it is not yet loaded.

Any hints?

thanks in advance,
 Waldemar


             reply	other threads:[~2017-10-10  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  9:12 Waldemar Brodkorb [this message]
2017-10-17 10:07 ` Heap corruption and crash reading syscall XML data Dmitry Antipov
2017-10-17 11:30   ` Pedro Alves
2017-10-17 11:43     ` Pedro Alves

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=20171010091214.GC7617@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=gdb@sourceware.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