public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/20020] GDB segfault on printing objects
Date: Fri, 10 Sep 2021 19:36:22 +0000	[thread overview]
Message-ID: <bug-20020-4717-dxGJhqamU5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20020-4717@http.sourceware.org/bugzilla/>

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

Mehmet gelisin <mehmetgelisin at aol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgelisin at aol dot com

--- Comment #33 from Mehmet gelisin <mehmetgelisin at aol dot com> ---
noticed while playing with abilint that the "Unknown file type given in input"
error message has no end of line character (LF or \n), so if you are passing
multiple files to abilint via xargs, you get all the output on one line. As far
as I can tell all the other errors printed by abilint contain and end of line
character (\n).

$ echo foo > foo
$ abilint --noout foo |& hd
00000000  61 62 69 6c 69 6e 74 3a  20 55 6e 6b 6e 6f 77 6e  |abilint: Unknown|
00000010  20 66 69 6c 65 20 74 79  70 65 20 67 69 76 65 6e  | file type given|
00000020  20 69 6e 20 69 6e 70 75  74 3a 20 66 6f 6f        | in input: foo|
0000002e
$ echo foo | hd
00000000  66 6f 6f 0a                                       |foo.|
00000004

$ grep -B2 -A1 'Unknown file type given in input' tools/abilint.cc
        case abigail::tools_utils::FILE_TYPE_UNKNOWN:
https://komiya-dental.com/ 
          emit_prefix(argv[0], cerr)
            << "Unknown file type given in input: " << opts.file_path;

noticed while playing with abilint that the "Unknown file type given in input"
error message has no end of line character (LF or \n), so if you are passing
multiple files to abilint via xargs, you get all the output on one line. As far
as I can tell all the other errors printed by abilint contain and end of line
character (\n). http://www.iu-bloomington.com/ 

$ echo foo > foo
$ abilint --noout foo |& hd
00000000  61 62 69 6c 69 6e 74 3a  20 55 6e 6b 6e 6f 77 6e  |abilint: Unknown|
00000010  20 66 69 6c 65 20 74 79  70 65 20 67 69 76 65 6e  | file type given|
00000020  20 69 6e 20 69 6e 70 75  74 3a 20 66 6f 6f        | in input: foo|
0000002e https://www.webb-dev.co.uk/ 
$ echo foo | hd
00000000  66 6f 6f 0a                                       |foo.|
00000004

$ grep -B2 -A1 'Unknown file type given in input' tools/abilint.cc
https://waytowhatsnext.com/  
        case abigail::tools_utils::FILE_TYPE_UNKNOWN:
          emit_prefix(argv[0], cerr)
            << "Unknown file type given in input: " << opts.file_path;

noticed while playing with abilint that the "Unknown file type given in input"
error message has no end of line character (LF or \n), so if you are passing
http://www.acpirateradio.co.uk/  multiple files to abilint via xargs, you get
all the output on one line. As far as I can tell all the other errors printed
by abilint contain and end of line character (\n).

$ echo foo > foo
$ abilint --noout foo |& hd
00000000  61 62 69 6c 69 6e http://www.logoarts.co.uk/  74 3a  20 55 6e 6b 6e
6f 77 6e  |abilint: Unknown|
00000010  20 66 69 6c 65 20 74 79  70 65 20 67 69 76 65 6e  | file type given|
00000020  20 69 6e 20 69 6e 70 75  74 3a 20 66 6f 6f        | in input: foo|
0000002e
$ echo foo | hd
00000000  66 6f 6f 0a                                       |foo.|
00000004 http://www.slipstone.co.uk/ 

$ grep -B2 -A1 'Unknown file type given in input' tools/abilint.cc
        case abigail::tools_utils::FILE_TYPE_UNKNOWN:
          emit_prefix(argv[0], cerr) http://embermanchester.uk/ 
            << "Unknown file type given in input: " << opts.file_path;

noticed while playing with abilint that the "Unknown file type given in input"
error message has no end of line character (LF or \n), http://connstr.net/  so
if you are passing multiple files to abilint via xargs, you get all the output
on one line. As far as I can tell all the other errors printed by abilint
contain and end of line character (\n). http://joerg.li/

$ echo foo > foo
$ abilint --noout foo |& hd
00000000  61 62 69 6c 69 6e 74 3a http://www.jopspeech.com/  20 55 6e 6b 6e 6f
77 6e  |abilint: Unknown|
00000010  20 66 69 6c 65 20 74 79  70 65 20 67 69 76 65 6e  | file type given|
00000020  20 69 6e 20 69 6e 70 75  74 3a 20 66 6f 6f        | in input: foo|
0000002e
$ echo foo | hd http://www.wearelondonmade.com/
00000000  66 6f 6f 0a                                       |foo.|
00000004
 http://www.compilatori.com/
$ grep -B2 -A1 'Unknown file type given in input' tools/abilint.cc
        case abigail::tools_utils::FILE_TYPE_UNKNOWN:
          emit_prefix(argv[0], cerr) http://www-look-4.com/
            << "Unknown file type given in input: " << opts.file_path;

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

  parent reply	other threads:[~2021-09-10 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20020-4717@http.sourceware.org/bugzilla/>
2020-04-07 23:51 ` ssbssa at sourceware dot org
2020-04-08 12:16 ` ssbssa at sourceware dot org
2021-08-19  6:03 ` ucelsanicin at yahoo dot com
2021-08-19 10:32 ` mark at klomp dot org
2021-09-10 19:36 ` mehmetgelisin at aol dot com [this message]
2021-11-10 14:16 ` bryanmcsp at gmail dot com

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-20020-4717-dxGJhqamU5@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).