Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Jonny Grant <jg@jguk.org>, gdb@sourceware.org
Subject: Re: gdb "Core was generated by" truncated to 80 characters
Date: Wed, 10 Jun 2020 22:32:12 -0400	[thread overview]
Message-ID: <1fee4331-12b1-839e-3782-43409729e7e9@simark.ca> (raw)
In-Reply-To: <b845f547-b0e5-ea50-4876-c8cb6e052a83@jguk.org>

On 2020-06-07 6:27 p.m., Jonny Grant wrote:
> 
> 
> On 26/05/2020 15:09, Simon Marchi wrote:
>> On 2020-05-26 7:07 a.m., Jonny Grant wrote:
>>> [Not sure if this got through to bug-gdb@gnu.org  so resending]
>>
>> gdb@sourceware.org is the right place.
>>
>>> Hello
>>>
>>> Just noticed my command line args of a core file are truncated, so it's hard to reproduce the crash as I don't know what the core was generated from.
>>>
>>> "Core was generated by" truncated to 80 characters in the below example.
>>>
>>> May I ask, is this a limitation of the kernel dump or gdb? When i use 'strings' I see the core does contain the full command line.
>>
>> You see the name of the process as dumped by the kernel, which truncates it at
>> a certain length.  Here's the corresponding code in the kernel, where you see it
>> limited at 80 characters:
>>
>> https://elixir.bootlin.com/linux/v5.6.14/source/include/uapi/linux/elfcore.h#L79
> 
> It's a shame that is so small, the arguments are visible when running I thought in ps aux. Do you know who is the 
> maintainer of that file please?

This is maintained in the Linux kernel.

https://www.kernel.org/doc/html/latest/process/development-process.html

Simon


      reply	other threads:[~2020-06-11  2:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 11:07 Jonny Grant
2020-05-26 14:09 ` Simon Marchi
2020-06-07 22:27   ` Jonny Grant
2020-06-11  2:32     ` Simon Marchi [this message]

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=1fee4331-12b1-839e-3782-43409729e7e9@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb@sourceware.org \
    --cc=jg@jguk.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