public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31524] Can't start program in Lazarus/fpc with activated debugging
Date: Sun, 24 Mar 2024 21:17:20 +0000	[thread overview]
Message-ID: <bug-31524-4717-MmTGzw87pp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31524-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31524

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Thanks for the log.  I see this:

  >> TCmdLineDebugger.SendCmdLn "-gdb-set language pascal"
...
  >> TCmdLineDebugger.SendCmdLn "ptype Shortstring"
  << TCmdLineDebugger.ReadLn "&"ptype Shortstring\n""
  << TCmdLineDebugger.ReadLn "~"type = ShortString = record \n""
  << TCmdLineDebugger.ReadLn "~"    length : BYTE;\n""
  << TCmdLineDebugger.ReadLn "&"\n\n""
  << TCmdLineDebugger.ReadLn "&"Fatal signal: ""
  << TCmdLineDebugger.ReadLn "&"Segmentation fault""

This output is clearly truncated and definitely a gdb bug.

I suspect it could be reproduced with just the executable.
If it's not too large, and if it's allowable, could you
attach it?

Could you say what Pascal compiler you are using?  I wonder
if maybe a test case with just the Shortstring type would
be possible to write -- we'll want a test case for the
patch anyway.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-24 21:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 20:12 [Bug gdb/31524] New: " reinhard.buchholz at arcor dot de
2024-03-22 16:43 ` [Bug gdb/31524] " tromey at sourceware dot org
2024-03-22 19:28 ` reinhard.buchholz at arcor dot de
2024-03-24 21:17 ` tromey at sourceware dot org [this message]
2024-03-25 19:48 ` reinhard.buchholz at arcor dot de
2024-03-25 20:05 ` reinhard.buchholz at arcor dot de
2024-03-25 20:19 ` reinhard.buchholz at arcor dot de
2024-03-25 22:41 ` tromey at sourceware dot org
2024-03-26 13:29 ` reinhard.buchholz at arcor dot de
2024-03-27  1:19 ` tromey at sourceware dot org
2024-03-27  3:40 ` tromey at sourceware dot org
2024-03-27 12:51 ` reinhard.buchholz at arcor dot de
2024-03-27 13:43 ` tromey at sourceware dot org
2024-03-27 16:42 ` tromey at sourceware dot org
2024-03-28 22:31 ` cvs-commit at gcc dot gnu.org
2024-03-28 22:32 ` tromey at sourceware dot org

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=bug-31524-4717-MmTGzw87pp@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).