This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix `return' of long/long-long results with no debuginfo
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: jan dot kratochvil at redhat dot com
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 11 Feb 2009 21:40:00 +0100 (CET)
- Subject: Re: [patch] Fix `return' of long/long-long results with no debuginfo
- References: <20090211194511.GA9324@host0.dyn.jankratochvil.net>
> Date: Wed, 11 Feb 2009 20:45:11 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Hi,
>
> the command `return' assumes `int' result when the current function has no
> debug info. This assumption breaks for example `void *' return on x86_64.
>
> Original bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=365111
>
> Regression-tested on x86_64-unknown-linux-gnu.
>
> This testcase also covers the previous fix of the `return' crash:
> http://sourceware.org/ml/gdb-patches/2009-01/msg00213.html
>
>
> Thanks,
> Jan
Sorry, this is wrong. Functions without return type implicitly return int.