Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ruedi Dummermuth <ruedi@abatron.ch>
To: Shaun Jackman <sjackman@pathwayconnect.com>
Cc: bgat@billgatliff.com,gdb@sources.redhat.com
Subject: Re: gdb signal normal termination of program
Date: Fri, 23 Nov 2001 08:56:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20011129081742.00bdf940@pop.abatron.ch> (raw)
In-Reply-To: <E1697Vx-0004um-00@dazed>

Hello Shaun

The BDI cannot detect when you enter the exit() function
unless you set a breakpoint in it. The BDI cannot generate
the message "Program terminated normally" because
it has no information about when this event happens.

Also an embedded application normally does not terminate.
When you finally burn you application into flash, it should
run continuously and will never terminate via exit().

You may change your exit() function and code-in the opcode
of a software breakpoint. If you did not change it within the
BDI configuration, the opcode for a breakpoint is 0xE7FFDEFE.

Regards,
Ruedi

At 09:24 28.11.2001 -0700, you wrote:
>Hello,
>
>I have an arm-elf target connected to a bdi2000 jtag debugger. Is there any
>instruction I can compile that indicates to the debugger or gdb that
>my program has reached normal termination. When main returns exit() is called
>which then hangs the processor. I have to interrupt it with ctrl-c. I'd like
>gdb to break to the prompt on its own and display the message "Program
>terminated normally". Do you know how I go about this?
>
>Thanks,
>Shaun

==============================
Ruedi Dummermuth
Abatron AG
Lettenstrasse 9
CH-6343 Rotkreuz
Switzerland
mailto:ruedi@abatron.ch
http://www.abatron.ch
Tel	++41 41 792 09 55
Fax	++41 41 792 09 60


WARNING: multiple messages have this Message-ID
From: Ruedi Dummermuth <ruedi@abatron.ch>
To: Shaun Jackman <sjackman@pathwayconnect.com>
Cc: bgat@billgatliff.com, gdb@sources.redhat.com
Subject: Re: gdb signal normal termination of program
Date: Wed, 28 Nov 2001 23:31:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20011129081742.00bdf940@pop.abatron.ch> (raw)
Message-ID: <20011128233100.SxWS51IsGL4vAaSj13cfvOT5Z76Q8Xa28QYFqrjaHaM@z> (raw)
In-Reply-To: <E1697Vx-0004um-00@dazed>

Hello Shaun

The BDI cannot detect when you enter the exit() function
unless you set a breakpoint in it. The BDI cannot generate
the message "Program terminated normally" because
it has no information about when this event happens.

Also an embedded application normally does not terminate.
When you finally burn you application into flash, it should
run continuously and will never terminate via exit().

You may change your exit() function and code-in the opcode
of a software breakpoint. If you did not change it within the
BDI configuration, the opcode for a breakpoint is 0xE7FFDEFE.

Regards,
Ruedi

At 09:24 28.11.2001 -0700, you wrote:
>Hello,
>
>I have an arm-elf target connected to a bdi2000 jtag debugger. Is there any
>instruction I can compile that indicates to the debugger or gdb that
>my program has reached normal termination. When main returns exit() is called
>which then hangs the processor. I have to interrupt it with ctrl-c. I'd like
>gdb to break to the prompt on its own and display the message "Program
>terminated normally". Do you know how I go about this?
>
>Thanks,
>Shaun

==============================
Ruedi Dummermuth
Abatron AG
Lettenstrasse 9
CH-6343 Rotkreuz
Switzerland
mailto:ruedi@abatron.ch
http://www.abatron.ch
Tel	++41 41 792 09 55
Fax	++41 41 792 09 60


  reply	other threads:[~2001-11-29  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  4:01 Shaun Jackman
2001-11-23  8:56 ` Ruedi Dummermuth [this message]
2001-11-28 23:31   ` Ruedi Dummermuth
2001-11-28  8:25 ` Shaun Jackman
2001-11-28  8:39 ` William A. Gatliff
2001-11-21  4:09   ` William A. Gatliff

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=4.2.0.58.20011129081742.00bdf940@pop.abatron.ch \
    --to=ruedi@abatron.ch \
    --cc=bgat@billgatliff.com \
    --cc=gdb@sources.redhat.com \
    --cc=sjackman@pathwayconnect.com \
    /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